fix: the way run_tests.sh works with arguments

Closes #50

See merge request !75

chore(deps): update all non-major dependencies

See merge request !71

See merge request !70

refactor: update cpu_idle and startup_cpu_boost defaults

See merge request !69

This commit updates the default values for the `cpu_idle` and
`startup_cpu_boost` properties the `resources` block inside
the `containers` block. The changes ensure that if these
properties are not explicitly set, they will default to `true` in
the `google_cloud_run_v2_service` resource.

ci: update CI templates versions

See merge request !68

feat: added load_balancer_backend variable to provide any custom options

Closes #53

See merge request !67

Allow ingress override when using load balancer

Closes #52

See merge request !66

There are some situations where it is valid to use
INGRESS_TRAFFIC_ALL in conjunction with the load balancer.
Currently it is not possible to override the
INGRESS_TRAFFIC_INTERNAL_LOAD_BALANCER ingress setting to
achieve this if var.enable_load_balancer == true.

ci: add SHORT_TEST_PREFIX variable

Closes #49

See merge request !64

Release 9.0

Closes #47

See merge request !63

This commit implements a matrix test job to run multiple
Terraform integration tests in parallel. It also implements
a cleanup script to ensure that failed test runs do not leave
infrastructure deployed which would cost money!

BREAKING CHANGE: migrate to cloud run v2 resources

There is no impact with this bump as the options we use are still supported.

The Cloud Run Domain Mapping service is still in Pre-GA status after
more than 3 years. Google's documentation now suggest using load balancers
or Firebase Hosting as an alternative as there are limitations with the domain mapping service.
We are removing it from this module as it seems as though it will soon be deprecated.

BREAKING CHANGE: Remove Cloud Run Domain Mapping

This commit refactors the uptime_monitoring module to no longer require
an additional "stackdriver" aliased google provider.
This was a source of confusion as it did some "magic" with regards to
passing project IDs around.
The two projects are now clearly defined as either `project` or
`monitoring_scoping_project` to avoid any confusion.