Use sourceLastUpdateTime in Update Dataset and File Metadata

[g-saracca]

What this PR does / why we need it:

Adds a mechanism to avoid two users updating same dataset version metadata and also same file metadata version.
Usese sourceLastUpdateTime query param for optimistic concurrency control. Depends on this js-dataverse PR.

Which issue(s) this PR closes:

• Closes Change internalVersionNumber to sourceLastUpdateTime in Update Dataset Metadata #841

Suggestions on how to test this:

Step 1: Run the Development Environment

1. Execute npm i.
2. Navigate with cd packages/design-system && npm i && npm run build.
3. Return with cd ../../.
4. Ensure you have a .env file similar to .env.example
5. Navigate with cd dev-env.
6. Start the environment using ./run-env.sh unstable.
7. To verify the environment, visit http://localhost:8000/ and check your local Dataverse installation.

Step 2:

Test the concurrency control in edit dataset metadata page.

1. Create a Dataset.
2. Once in the Dataset Page, click Edit Dataset -> Metadata to open it in a new tab and then click it to open it in the same tab.
3. In the same tab, edit something and save, should succeed.
4. After that; in the new tab, edit something and save, should fail thanks to this control. Something like "Internal version timestamp [ISO date] is outdated.

Test the concurrency control in edit file metadata page.

1. Upload a file to the recently created dataset.
2. Open the edit file metadata page in two tabs.
3. In the first tab, edit something and save, should succeed.
4. After that; in the second tab, edit something and save, should fail also thanks to this control.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No.

Is there a release notes or changelog update needed for this change?:

Yes, added.

[coveralls]

coverage: 97.223% (+0.02%) from 97.207%
when pulling 2bcbc00 on 841-change-internalVersionNumber-to-sourceLastUpdateTime-in-update-dataset-metadata
into cd0b794 on develop.

[Copilot]

Pull Request Overview

This PR implements optimistic concurrency control for dataset and file metadata editing by replacing internal version numbers with last update timestamps. The changes prevent concurrent editing conflicts by using the sourceLastUpdateTime query parameter to ensure users are editing the most recent version of the metadata.

• Replaces datasetInternalVersionNumber parameter with datasetLastUpdateTime across all dataset metadata forms
• Updates file metadata editing to include datasetLastUpdateTime for concurrency control
• Adds lastUpdateTime field to DatasetVersion model for tracking version timestamps

Reviewed Changes

Copilot reviewed 50 out of 52 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/dataset/domain/models/Dataset.ts	Adds lastUpdateTime field to DatasetVersion model
src/sections/shared/form/DatasetMetadataForm/index.tsx	Replaces datasetInternalVersionNumber prop with datasetLastUpdateTime
src/sections/edit-file-metadata/EditFilesList.tsx	Adds datasetLastUpdateTime prop for file metadata concurrency control
src/files/domain/useCases/editFileMetadata.ts	Updates to accept sourceLastUpdateTime parameter
tests/component/sections/shared/dataset-metadata-form/DatasetMetadataForm.spec.tsx	Updates test cases to use datasetLastUpdateTime instead of internalVersionNumber

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[ChengShi-1]

looks good

[ofahimIQSS]

very nice - merging!