container: use project_id from provider configuration

[Gnoale]

As a user bring recently, in most of the modules, we ignore the project_id parameter set at the provider level in some cases, because the environment takes precedence over the provider config here

partly fixes #3068

The provider configuration should probably override other configuration sources but this could be impactful / breaking for users used to provide environment variables

The change imply to explicitly find a project_id at the resource / client level and raise an error if not found, instead of relying on the SDK logic to eventually find it or use an empty string in some cases.

=> Now when running the test in CI, we need to inject a project ID in the meta configuration.

But this reveal another corner case: resources calling HTTP GET query with the optional project_id parameter that where not using it, namespace container datasource for instance, are now using the fake project_id set in the test suite (&project_id=1111111).
So we strip this parameter from the query to address these kind of cases

[remyleone]

Is there a way to ensure that it is taken into account with a test?

[Gnoale]

the test would break without the ForceProjectID in meta.Config

[Gnoale]

Closing for now