jsii releases are no longer from a trusted publisher

https://github.com/aws/jsii-compiler/pull/2465, which was released with v5.9.18, configured trusted publishing. That seems to have been disabled in https://github.com/aws/jsii-compiler/pull/2626. Publishes are now done with a long-lived token (`NODE_AUTH_TOKEN`).

This means that consumers using pnpm with [trustPolicy: no-downgrade](https://pnpm.io/settings#trustpolicy) get an error when attempting to install recent versions. The unfortunate reality is that once a package is published with trusted publishing, all subsequent versions need it or else clients may complain about trust being downgraded.

> [ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for "jsii@5.9.44" (possible package takeover)

See https://cdk-dev.slack.com/archives/C01C8R4K2E6/p1780675977611519?thread_ts=1779896079.602189&cid=C01C8R4K2E6

This issue is similar to #2651, but that was about downgrading provenance. That was fixed in #2652, but the trusted publishing downgrade is still present.

Compare the trusted-publishing setup introduced in PR 2465 with the release configuration changed in PR 2626, using the NODE_AUTH_TOKEN reference as the starting point. Reproduce installation with pnpm trustPolicy: no-downgrade and confirm that subsequent jsii releases use trusted publishing without an ERR_PNPM_TRUST_DOWNGRADE error.

Written by the indexing model from the issue text.