[Tech Debt] Update CI concurrency settings to avoid unexpected CI run cancellations

[mikealfare]

Is this a new bug in dbt-bigquery?

• I believe this is a new bug in dbt-bigquery
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Arbitrary CI runs are are being cancelled, resulting in false positive alerts in our alerts channel. I believe this is happening because we now support testing changes in other repos (e.g. dbt-core and dbt-adapters) against dbt-bigquery, which results in runs with the same concurrency criteria.

Expected Behavior

We should support integration testing for this new use case and allow them to run in parallel.

Steps To Reproduce

There are several examples of recent runs in the alerts channel. I expect that if a workflow that uses dbt-bigquery's integration.yaml in dbt-core is triggered while a scheduled release branch test is already running in dbt-bigquery, the scheduled release branch test will get cancelled.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-bigquery:

Additional Context

No response