owner metadatafield check for all languages

[floriangantner]

References

• Fixes https://github.com/4Science/DSpace/issues/325

Description

• align the owner metadatafield check to consider all metadata languages and not only the values without language. This is also used in the regarding services which check all languages of this metadatafield. (see ResearcherProfileServiceImpl & Co https://github.com/4Science/DSpace/blob/efc9ceacb9432b232742ff02df137da42b43bde1/dspace-api/src/main/java/org/dspace/profile/ResearcherProfileServiceImpl.java#L211 ).

Instructions for Reviewers

List of changes in this PR:

• change get owner metadata to allow all metadata languages, not only owner metadata without metadata languages (=null).

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

• owners with metadata language might be created during the migration (ItemImport), where the default.language configuration parameter is applied.
• in otherworkspace, owners with metadatalanguage are currently not indexed so this functionality is not shown correctly to the regarding users.
• owners with metadatalanguage are unable to push some item to orcid, because they have no permission.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• [x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
• [ ] My PR passes Checkstyle validation based on the Code Style Guide.
• [ ] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
• [ ] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
• [ ] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• [ ] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.