When using the default value to `true` some new projects
got this setting enabled while the feature was not fully
implemented. To fix this we need to reset any enabled
settings to `false` until the feature about
`job_token_scope_enabled` is fully available.

Changelog: fixed