Cherry Pick #32178: Loose BigQuery GCP project ID regex restrictions

[kberezin-nshl]

Cherry pick of this PR: #32178

cc @lostluck

[lostluck]

It does not make the cut to require a new RC to be generated (it's clearly not a release blocker), but it's also so small in scope to not be a problem.

So what will happen is I'll look at this again in the morning, and most likely merge it in. That way, if there's a release blocking issue in RC1, it will be included in RC2. Otherwise it'll have to wait until 2.60.0.

[kberezin-nshl]

Great, thank you @lostluck .

It is quite a big annoyance for us, so we'd appreciate removing our dirty hacks to work that around after migrating to 2.59. But obviously not that a big deal because we have workarounds in place.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @m-trieu for label java.
R: @shunping for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[shunping]

LGTM

[github-actions]

R: @damondouglas for final approval

[lostluck]

Due to the conditional nature of the cherry pick, It should not be added to the release milestone at this time. It may or may not make it into 2.59.0, per reasons I stated above. It will be a part of 2.60.0 though.