Change CI_JOB_TOKEN secure workflow default to enable for new projects

Problem to solve

During rollout of the CI_JOB_TOKEN Secure workflow we discovered users weren't interested in implementing the feature since it was considered a breaking change. After dogfooding and having a few users test the feature in %14.3 and %14.4, we are now ready to enable the feature by default for new projects

Proposal

• Change project_ci_cd_settings.job_token_scope_enabled default from false to true.
• Ensure documentation and troubleshooting is in place for users to understand their possible pipeline failures.