[FEATURE] Allow to set up trusted publishing for @scope/* #8877
Description
Hello! This is related to #8544
I have ~500 packages (here) and publish more packages as Google releases new APIs or new API versions (npm package version is used for generator updates and API revisions, also Google API versions can be anything non-semver).
All of them follow this naming pattern: @maxim_mazurok/gapi.client.*, for example @maxim_mazurok/gapi.client.drive-v3.
Release process is fully automated, and until recently I was using long-lived legacy token.
Now I don't want to update the token every 90d manually. I would rather use trusted publishing, especially since I have provenance already set up.
The obstacle I see is having to manually configure each package (~500) via npm UI. And then also having to do that for each new package (when new APIs or versions are released by Google).
I would much rather set it up once for the whole scope/namespace @maxim_mazurok/*.
As a workaround, I might explore automating the process using my login/password and 2fa seed from CI. However that seems to be about as secure as previous full-access long-lived legacy token.
Would appreciate it if you could allow my use-case to be solved to support low-maintenance automation that I have going on.
Thank you!