chore(ci): enables npm trusted publishing for juno-messages-provider

[hodanoori]

Summary

Updates the npm version because npm must be ≥ 11.5.1 for trusted publishing to work. In addition I added the registry URL to the release workflow to ensure that all publish operations during CI explicitly target the public npm registry, avoiding any interference from other registry settings and aligning with npm’s trusted publishing expectations.

Changes Made

• Updated the release GitHub Actions workflow to configure the npm registry and upgrade npm before running the Changesets publish step
• Adjusted the @cloudoperators/juno-messages-provider package.json to use the monorepo root Git repository URL and add a publishConfig pointing to the public npm registry with public access

Related Issues

Issue 1: #1405

Screenshots (if applicable)

Testing Instructions

1. pnpm i
2. pnpm TASK

Checklist

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have created a changeset for my changes.

PR Manifesto

Review the PR Manifesto for best practises.

[changeset-bot]

🦋 Changeset detected

Latest commit: 2170180

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@cloudoperators/juno-messages-provider	Patch
@cloudoperators/juno-app-doop	Patch
@cloudoperators/juno-app-example	Patch
@cloudoperators/juno-app-greenhouse	Patch
@cloudoperators/juno-app-supernova	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR