ci: migrate to OIDC Trusted Publishing

[tanjeemh]

What problem are we solving?
As npm has let us know that they are revoking all classic npm-tokens this month, we are migrating to using OIDC Trusted Publishing instead.

Why are we solving it this way?

• id-token: write permissions is required for OIDC authentication
• set a Github Environment called publish-bitcoinjslib for secure deployments to the master branch
• ensure npm is at least up to v11.5.1 for OIDC Trusted Publishing compatibility
• update semantic-release package for whoami bug fix support
• ignore base-x,cipher-base and sha.js vulnerabilities from npm audit

Ticket: DX-2098