Changes for trusted publishing

[annamcallister]

Only one workflow can be the npm "trusted publisher"- this is going to be release-solidity-package.yaml, meaning the zeto-contracts package for a release must be published as a manual step after the main release workflow.

I have

• removed the call from release.yaml to release-solidity-package.yaml
• stopped release-solidity-package.yaml from being triggered by workflow dispatch- this can no longer work as the caller will not be the trusted publisher
• modified release-solidity-package.yaml to install the latest npm version (> 11.5.1) which is required for trusted publishing- this also requires node 22 to be installed
• removed continue on error from the publish step- this is irrelevant in a direct call to the workflow
• set continue on error to true for the dist tags step because this has been broken by trusted publishing, but the community response to this break leads me to think it will be fixed soon, so optimistically running this step but ignoring the results seems like the best short term way forwards