Editor / Associated resource / Update panel based on type config

[fxprunayre]

If one config was using the metadataStore source, then this source was never hidden when other types are opening the panel.

Follow up of #7669

eg. in the following config, linkToParent allows metadataStore source, but opening linkToPlatform will also show it even if it is only configured with DOI or remote URL sources.

<section>

          <action type="associatedResource"
                  name="linkToParent"
                  btnClass="fa gn-icon-series"
                  process="siblings">
            <directiveAttributes>{"fields": {"associationType": "largerWorkCitation", "initiativeType": "" },
              "sources": {"metadataStore": {"params": {"isTemplate": "n"}},
              "remoteurl": {"multiple": true}
              }}</directiveAttributes>
          </action>


          <action type="associatedResource"
                  name="sextant-linkToPlatform"
                  btnClass="fa fa-ship"
                  process="siblings">
            <directiveAttributes>{"fields": {"associationType": "crossReference", "initiativeType": "platform" },
              "sources": {"doiapi": {"url": "https://api.datacite.org/dois",
              "params": {"prefix": "10.17600", "query": "titles.title:{query}* OR doi:{query}"}}
              }}</directiveAttributes>
          </action>

          <directive data-gn-associated-resources-panel="gnCurrentEdit.metadata"
                     data-editor-config="sextant"/>
        </section>

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

Funded by Ifremer

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[josegar74]

Tested, works fine.