feat(explore): Add logs export modal with row limit

[JoshuaKGoldberg]

Previously, all logs data exports were done with a LogsExportButton -> ExploreExport component -> DataExport component, which used a useDataExport hook internal to its file. This PR adds a LogsExportSwitch button on top of that which can opt into a new LogsExportModalButton if a ourlogs-modal-export feature flag is enabled, or ?logsModalExport=true is in query params.

LogsExportModalButton takes in the same general data and, on click, renders a new LogsExportModal. That modal component calls to the newly exported useDataExport hook.

useDataExport is also now augmented to:

• Download logs locally if we know we're below the 1k page size limit
• Download a file directly if given it as fileName from the server

In other words, previously:

LogsExportButton -> ExploreExport -> DataExport -> useDataExport

Now:

                     -> LogsExportButton -> ExploreExport -> DataExport -
                   /                                                      \
LogsExportSwitch -                                                         -> useDataExport
                   \                                                      /
                     ---> LogsExportModalButton ---> LogsExportModal ----

I also extracted a downloadFromHref used in both the CSV and JSON paths.

This was used for LOGS-690. Fixes LOGS-692.

[sentry]

Sentry Snapshot Testing

Name	Added	Removed	Modified	Renamed	Unchanged	Status
sentry-frontend sentry-frontend	0	0	0	0	204	✅ Unchanged

⚙️ sentry-frontend Snapshot Settings

[linear-code]

LOGS-690 Create reference draft of modal export with initial phrasing

LOGS-692 Implement designs for logs export modal

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[JoshuaKGoldberg]

Once #112953 is in & we've validated on prod, I'll switch this to rely on allColumns. Currently blocked on some errors in Snuba-land.

[JoshuaKGoldberg]

[Todo] Telemetry: other parts of the flow have pre-existing logs; I'll need to add some corresponding ones.