Fix yarn authentication in release CI (option 1)

[Totto16]

This is a follow up of #64

Since I tested #64 at the beginning with npm, setting the enviornment variable NPM_TOKEN was enough, as npm picked that up, but yarn doesn't do that and it needs the setting npmAuthToken in the .yarnrc.yml settings file to be set correctly.

But when you use that in the CI, the release CI and build CI fail, as NPM_TOKEN is not set everywhere, so it has a default empty value in the CI's .

I tested this entirely with a private registry and it works.

This is one possible fix of the release CI, see #72 for the 2. option (which doesn't work)

[Totto16]

I did one final test (from this branch) and it works (finally 🎉 ) https://github.com/gjsify/gnome-shell/actions/runs/17010760574/job/48226492645

[JumpLink]

I did one final test (from this branch) and it works (finally 🎉 ) https://github.com/gjsify/gnome-shell/actions/runs/17010760574/job/48226492645

Nice, thank you very much 🎉

[Totto16]

I made a small mistake, so the provenance was attributed to this branch and not the main branch 😓
(See https://search.sigstore.dev/?logIndex=402476839)

So I deleted the npm version, but you can't republish it again)
So in needed to bump the version to 48.0.4 😓

The attestation can be viewed e.g. here https://registry.npmjs.org/-/npm/v1/attestations/@girs%[email protected]
or here https://www.npmjs.com/package/@girs/gnome-shell#provenance
or here https://search.sigstore.dev/?logIndex=402672235