[Task] Sub-Issue 2: Apply User-Triggered UI Sorting to exported files

[Steffengreiner]

What's the issue?

Context
When a user applies a custom sort to a grid in the UI (e.g. by clicking a column header), that sort order is currently not carried over into the exported files.
This means the sheet the user receives may be ordered differently from what they were looking at in the UI, making it harder to work with the exported data.
The expected behaviour is that the exported sheet always mirrors the current sort state of the grid at the time of export

Current Behaviour
When a user applies a custom column sort in the following UI elements:

1.) Sample grid,
2.) Measurement grid
3.) Raw data grid

and then downloads the metadata sheet, the downloaded sheet does not reflect the user's chosen sort order within the UI

Expected Behaviour
When a user exports a metadata sheet after having applied a custom sort in the UI grid,
the downloaded sheet reflects the sort order that was active in the grid at the time of the export.

Acceptance Criteria

• Given a user has sorted the sample grid by a custom column, when they download the edit metadata sheet or the full export sheet, then the rows in the downloaded sheet are ordered according to the active UI sort.
• Given a user has sorted the measurement grid by a custom column, when they download the edit metadata sheet or the full export sheet, then the rows in the downloaded sheet are ordered according to the active UI sort.
• Given a user has sorted the raw data grid by a custom column, when they download the Download URL List, then the URLs in the downloaded text file are ordered according to the active UI sort.
• Given a user has not applied any custom sort, when they download a sheet, then the default ascending sort by ID (as defined in sub-issue 1) is applied — this behaviour is unchanged.

Code of Conduct

• I agree to follow this project's Code of Conduct