Resolve "Support loading secrets directly into services"

Closes #20

See merge request !25

Merge branch '18-terraform-always-wants-to-add-metadata-annotation-run-googleapis-com-launch-stage-beta' into 'master'

Resolve "Terraform always wants to add  metadata annotation "run.googleapis.com/launch-stage"   = "BETA""

Closes #18

See merge request !24

Do not remove the BETA stage as we are going to still use some BETA options like the mounting of secrets from GCP Secret Manager

use gvisor instead of placeholder

Closes #17

See merge request !23

Update changelog for 2.0.3

See merge request !22

Add flag to stop egress ip being destroyed

Closes #16

See merge request !21

Update changelog

See merge request !20

Configure monitoring authentication proxy for instances which require authentication

See merge request !19

add additional attrbutes to ignore changes list

See merge request !17

Allow static egress ip

Closes #15

See merge request !18

There are a few more attributes which Google has started using
internally to record state. Add them to the ignore changes list so that
terraform won't keep wanting to change resources.

Part of uis/devops/raven/infrastructure#32

make use of our common monitoring module

Closes #13

See merge request !15

Rather than ship our own monitoring module, make use of the
gcp-site-monitoring module. This effectively makes this module require
0.13 so a major version bump is required.

Closes #13

Use Google Beta provider to allow for min-scale option

See merge request !16

allow ingress type to be specified

See merge request !13

It would appear that the "run.googleapis.com/ingress" annotation can be
set to "all" without having to enable the beta launch stage. Indeed it
*has* to be set to "all" since attempting to unset it causes Cloud Run
to immediately reset it.

The "run.googleapis.com/ingress-status" annotation is maintained by the
infrastructure Google-side so ignore changes to it.

Add support for minimum Cloud Run container instances (`min_scale`)

Closes #12

See merge request !14

Provide a variable which allows ingress type to be specified. This
allows placing the service behind Cloud Load Balancer.

Provide variables which allow extra annotations to be added to the Cloud
Run service and the service template.

allow stackdriver host project to differ from monitored project

Closes #11

See merge request !12

As noted in #11, we do not support the common case where a single
Stackdriver workspace hosts multiple projects. Do this by requiring a
Google provider for the Stackdriver workspace be passed to the module is
alerting is enabled.

We use a separate provider because the provider used must be able to
create monitoring resources *in the host project*. In the case of our
standard deployment, this implies it needs *product admin* credentials.

We no longer need to enable the monitoring service since this service a)
needs to be enabled in the *host* project and b) the service will have
been enabled as a necessary side-effect of creating the Stackdriver
workspace.

Closes #11