Add acceptance tests for how provider handles scopes argument

[modular-magician]

This PR adds acceptance tests for usage of scopes that demonstrate:

• how the provider behaves when provider configuration arguments come from different sources ( config vs ENVs)
  • There are no ENVs for scopes
  • There is a default set of scopes used if the argument isn't supplied
• schema-level validation that's in place
  • There isn't any validation about empty lists, instead the empty list is ignored
• use cases: how does this argument impact the providers behaviour in plan/apply
  • I've implemented a test case where setting the scopes to incorrect values causes provisioning to fail.

Release Note Template for Downstream PRs (will be copied)

Derived from GoogleCloudPlatform/magic-modules#11860

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.