[meta] revisit scopes

Tl;dr, let's limit our usage of scopes to the restricted set, and determine non-restricted behavior/format/action based on task.payload.

Details:

Our usage of scopes came from the original funsize signingworker, which used scopes to determine the type of cert (dep/nightly/release), as well as the signing format (gpg/authenticode/dmg etc). With CoT, we restricted the cert scope, allowing for dep but restricting nightly and release to certain trees. Over time, we found that using scopes for formats was unwieldy, without seeing any benefit. We moved to specifying format in the task payload, and only setting the cert scope.

Let's continue this pattern throughout the scripts. Restricted scope types (e.g., balrog server, signing cert level, beetmover bucket) should continue to be scopes, and we should continue restricting them in scriptworker.constants.DEFAULT_CONFIG.cot_restricted_scopes. Any other scopes, we should deprecate, and move those settings into the task payload.

(To clarify: in the current proposal, all of cert:dep-signing, cert:nightly-signing, and cert:release-signing would each be scopes, even though only the latter 2 are restricted. We're just talking about removing the format scopes, for signing.)

Let's resolve this issue once all scripts follow this pattern.

Verifica la gestione degli scope in tutti gli script, iniziando da scriptworker.constants.DEFAULT_CONFIG.cot_restricted_scopes e dai dati task.payload descritti nell’issue. Confronta il comportamento degli script di signing e degli altri script con il modello degli restricted scope. Il lavoro è completato quando le impostazioni con restrizioni rimangono scope, mentre le altre impostazioni sono rappresentate in task.payload e l’uso degli scope indicato nell’issue è risolto in tutti gli script.