Rename to reflect outbound scope direction

What does this MR do and why?

Rename project.ci_job_token_scope_enabled to project.ci_outbound_job_token_scope_enabled

We expose this as job_token_scope_enabled in the graphql api and ci_job_token_scope_enabled in the REST api, we could deprecate this in favor of outbound_job_token_scope_enabled and ci_outbound_job_token_scope_enabled eventually, but for the REST API this needs to be in a major release as a breaking change.

How to set up and validate locally

Run the tests, it's a refactor 😄

You could play with the job token scope feature and make sure it all still works. 🎚

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.