Add save-to-server option for linelist exports

[joshsadam]

What does this PR do and why?

Adds a save-to-server option to the v2 linelist export dialog. Users can still download CSV/XLSX exports locally, or save the generated export as a ready data export that can be opened later from the data exports page.

This also adds GraphQL support for client-side linelist row loading, direct-upload-backed linelist export creation, and JavaScript test coverage for the v2 client export flow.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other pull requests.

How to set up and validate locally

1. Enable the v2 client linelist export feature flag:

   bin/rails console
   Flipper.enable(:client_linelist_exports_v1)

2. Start the app with bin/dev.
3. Open a project samples page, for example http://localhost:3000/<group>/<project>/samples.
4. Select one or more samples, open the actions dropdown, and choose Linelist Export.
5. Verify the default flow still downloads locally when Save export to server is unchecked.
6. Check Save export to server, enter a name, export both CSV and XLSX, and verify the progress window shows a saved-export link.
7. Break the upload path and confirm Retry upload and Download locally instead work for the failed save-to-server flow.
8. Run the focused checks:

   bin/rails test test/graphql/create_linelist_data_export_test.rb test/graphql/linelist_export_rows_query_test.rb test/services/data_exports/linelist_create_service_test.rb
   bin/rails test:system test/system/data_exports_test.rb
   pnpm run test:js
   node --check app/javascript/controllers/linelist_export_controller.js

PR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the PR acceptance checklist for this PR.

[joshsadam]

Addressed #1805 (comment). Fix in fe9f8b9

[joshsadam]

Addressed #1805 (comment). Fix in 64c56ca

[ChrisHuynh333]

Seems to work well. In addition to what we discussed, just a couple phrasing things I think should be changed (up to you!)

[ChrisHuynh333]

Some issues to dig into:

• User with shared guest access to a sample can export the sample locally, bypassing permissions check. Permissions blocks this if trying to save to the server.
  • To recreate: with user1, create a group + project + sample. On user2, create a group + project + sample, and then at the group level, invite user1's group at guest level. Re login as user1, go to user1's group, and export both samples without saving to server.
• I'm having a failed export (not saving to server) on user1 when exporting from a group containing/shared to all samples (with new seed). Error is: An object of type Sample was hidden due to permissions. I believe user1 has at least analyst access to all samples, and this export works fine on main.

[joshsadam]

Some issues to dig into:

• User with shared guest access to a sample can export the sample locally, bypassing permissions check. Permissions blocks this if trying to save to the server.

  • To recreate: with user1, create a group + project + sample. On user2, create a group + project + sample, and then at the group level, invite user1's group at guest level. Re login as user1, go to user1's group, and export both samples without saving to server.

• I'm having a failed export (not saving to server) on user1 when exporting from a group containing/shared to all samples (with new seed). Error is: An object of type Sample was hidden due to permissions. I believe user1 has at least analyst access to all samples, and this export works fine on main.

Think I got this sorted out now: