Standard / ISO19115-3 / Improve linking to parent

[fxprunayre]

In ISO19115-3, linking to parent are most of the time done using associated resources with specific association type (partOfSeamlessDatabase by default, but also series or largerWorkCitation). This can be configured in the plugin but some users have a mix of "old" encoding using parentMetadata element.

   <mdb:parentMetadata uuidref="fa6e13d4-5700-4391-a472-dd29b82ba3db"
                       xlink:title="REMI Network Observation and Monitoring Locations"/>

Now the default encoding is:

   <mri:associatedResource>
      <mri:MD_AssociatedResource>
         <mri:associationType>
            <mri:DS_AssociationTypeCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#DS_AssociationTypeCode"
                                        codeListValue="partOfSeamlessDatabase"/>
         </mri:associationType>
         <mri:metadataReference uuidref="0aa26e4e-4e10-4986-a433-986c2d247669"
                                xlink:href="http://localhost:8080/geonetwork/srv/api/records/0aa26e4e-4e10-4986-a433-986c2d247669"/>
      </mri:MD_AssociatedResource>
   </mri:associatedResource>

This fix the case of a mix of encoding is used for encoding parent relationships and display in the editor associated resource panel a parent block with either parentMetadata or associatedResource. When removing a parent relation, the parent-remove.xsl process handle both encoding. New links are created based on the current plugin configuration. Record view shows both.

Funded by Ifremer

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud