Handle FileSummary rendering using local state

[nozomione]

Context

Epic: #358

Currently, when a user changes the download options for regenerating a dataset, a new dataset ID is generated.

This ID is then used to update the File Summary section UI (in green) and for the dataset download via API requests.

We want to streamline this process by handling the File Summary section UI updates using a local state, without generating a new dataset ID, until the user actually initiates the dataset regeneration by clicking the Regenerate Dataset button.

Route: /dataset/id - the UI should update using the local state without making an API request:

Problem or idea

We should manage changes to download options and the File Summary section UI updates using local state, without relying on API requests. This approach will enable the UI to immediately reflect user selections, enhancing the overall user experience.

These changes should support both the /download(for My Dataset) and dataset/id (all other dataset types) routes, and all shared components and methods should be updated accordingly.

Route: /download for My Dataset - the UI is updated using API requests to preserve the user's download options preference for their dataset, which is our current flow:

Solution or next step

1. Add a new local state, regeneratedDataset, in FileSummary to handle the data swap in the UI on download options change for regenerate datasets
2. Clean up the no longer used global context state regeneratedDataset (replaced by the local state above) from all contexts/hooks
3. Adjust useDatasetManager hook methods for the processing dataset and the download options updates to support both /doownload and /dataset/id routes based on the changes made in steps 1 and 2
4. Update the shared DownloadOptionsForm component to finalize the implementation for the local state update for regeneratedDataset
5. Refactor FileSummary to support these changes