Update npm publication workflow

[rknj]

Apply the changes (detailed in the parent ticket) for:

• https://www.npmjs.com/package/@jahia/create-module
• https://www.npmjs.com/package/@jahia/vite-plugin
• https://www.npmjs.com/package/@jahia/javascript-modules-library

[GauBen]

I took a quick a look hoping it would be a basic fix but it's not that simple: we have two workflows that publish to NPM

• javascript-modules/.github/workflows/on-release.yml

  Lines 41 to 53 in db15e4f

  	- uses: jahia/jahia-modules-action/release@v2
  	name: Release Module
  	with:
  	github_slug: Jahia/javascript-modules
  	primary_release_branch: main
  	release_id: ${{ github.event.release.id }}
  	release_version: ${{ github.event.release.tag_name }}
  	github_api_token: ${{ secrets.GH_API_TOKEN }}
  	nexus_username: ${{ secrets.NEXUS_USERNAME }}
  	nexus_password: ${{ secrets.NEXUS_PASSWORD }}
  	mvn_settings_filepath: ".github/maven.settings.xml"
  	slack-webhook-qa: ${{ secrets.SLACK_WEBHOOK_URL_RC_FOR_QA }}
  	npmjs_publish_token: ${{ secrets.NPMJS_PUBLISH_TOKEN }}

• javascript-modules/.github/workflows/on-merge.yml

  Lines 88 to 98 in db15e4f

  	- name: Setup .yarnrc.yml file to allow publication to https://registry.npmjs.org with a 'yarn npm publish'
  	shell: bash
  	run: |
  	echo "npmAuthToken: ${{ secrets.NPMJS_PUBLISH_TOKEN }}" >> ~/.yarnrc.yml
  	- uses: jahia/jahia-modules-action/publish@v2
  	with:
  	# the test module is built as part of the Maven build
  	tests_module_type: "disabled"
  	nexus_username: ${{ secrets.NEXUS_USERNAME }}
  	nexus_password: ${{ secrets.NEXUS_PASSWORD }}
  	mvn_settings_filepath: ".github/maven.settings.xml"

Trusted publishing only supports a single workflow file, so we have to rethink our workflows to enable trusted publishing.

In the meantime, because publication is broken, I have created a temporary (3 month) token, and moved this task to "Next month".