Deploy token scope can cause confusion

Problem to solve

When creating a deploy token, if the container registry is not enabled, users are forced to select a scope even though there is only 1 option available, and it is required. This can cause confusion and is not a good user experience.

Intended users

Sasha (Software Developer) Devon (DevOps Engineer)

Further details

Proposal

When only a single option is available, default to read_repository being checked. This option should also be disabled since deselecting it would cause an error.

What does success look like, and how can we measure that?

When a user creates a deploy token and only one scope is available, they are presented with a simpler, less confusing flow.