Issue 1319: do not copy dc.identifier.doi metadata when new item version is created

[kuchtiak-ufal]

No description provided.

[Copilot]

Pull request overview

This pull request addresses Issue 1319 by preventing DOI (Digital Object Identifier) metadata from being copied when a new item version is created in DSpace. The change ensures that each version of an item can receive its own unique DOI identifier, similar to how handle identifiers (dc.identifier.uri) are currently handled.

Changes:

• Added dc.identifier.doi to the list of ignored metadata fields during item versioning
• Added test coverage to verify that DOI metadata is not copied to new versions

Reviewed changes

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

File	Description
dspace/config/spring/api/versioning-service.xml	Added dc.identifier.doi to the ignoredMetadataFields set in the versioning service configuration, preventing DOI metadata from being copied during version creation
dspace-api/src/test/java/org/dspace/identifier/ClarinVersionedHandleIdentifierProviderIT.java	Enhanced existing test to simulate DOI metadata on the original item and verify it is not copied to the new version

[port-pr]

Backport failed for dtq-dev, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch downstream dtq-dev
git worktree add -d .worktree/backport-1320-to-dtq-dev downstream/dtq-dev
cd .worktree/backport-1320-to-dtq-dev
git switch --create backport-1320-to-dtq-dev
git cherry-pick -x 1b7ed17228c5f1260b250361fa87f49d9af0e14a