Skip publishing helper DCAT script as artifact

[Flor Chacón (florelis)]

Summary of the Pull Request

The build pipeline fails to create the DCAT pipeline artifacts because it tries to publish a helper script that isn't signed. Since this script doesn't do much and it is only used internally, it doesn't seem worth it to set up signing for it. So, I'm just removing it from the published files.

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

[Copilot]

Pull request overview

Removes an unsigned helper PowerShell script from the DCAT stage’s published output so artifact publication doesn’t fail due to code-signing validation, while still generating the required DCAT submission JSON metadata.

Changes:

• Stop copying Update-DcatSubmission.ps1 into the DCAT output directory/artifact.
• Keep generating DCAT JSON metadata via New-DcatSubmission.ps1 and publish only the resulting JSON set.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.