Monitoring: docstring changes, 'account' -> 'workspace', via synth.

[yoshi-automation]

This PR was generated using Autosynth. 🌈

Here's the log from Synthtool:

synthtool > Cloning googleapis. synthtool > Running generator for google/monitoring/artman_monitoring.yaml. synthtool > Ensuring dependencies. synthtool > Pulling artman image. latest: Pulling from googleapis/artman Digest: sha256:229601142daed005bf56fbaa21a02cf7aa0b261b57677d38306f8013e536de7a Status: Image is up to date for googleapis/artman:latest synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3. synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/group_service_client.py. synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/notification_channel_service_client.py. synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/uptime_check_service_client.py. synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/metric_service_client.py. synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py. synthtool > Replaced '(^.*$\\n)*' in google/cloud/monitoring_v3/proto/common_pb2.py. synthtool > No replacements made in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py for pattern then a new `\[CONDITION_ID\]` is created. , maybe replacement is not longer needed? synthtool > Replaced ' ::\n\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py. synthtool > Replaced '^(\\s+)have an ``id`` label: :: resource.type =\n.*' in google/cloud/monitoring_v3/proto/metric_service_pb2.py. synthtool > Replaced 'return google.api_core.grpc_helpers.create_channel\\(\n(\\s+)address,\n\\s+credentials=.*,\n\\s+scopes=.*,\n' in google/cloud/monitoring_v3/gapic/transports/uptime_check_service_grpc_transport.py. synthtool > Replaced 'return google.api_core.grpc_helpers.create_channel\\(\n(\\s+)address,\n\\s+credentials=.*,\n\\s+scopes=.*,\n' in google/cloud/monitoring_v3/gapic/transports/metric_service_grpc_transport.py. synthtool > Replaced 'return google.api_core.grpc_helpers.create_channel\\(\n(\\s+)address,\n\\s+credentials=.*,\n\\s+scopes=.*,\n' in google/cloud/monitoring_v3/gapic/transports/alert_policy_service_grpc_transport.py. synthtool > Replaced 'return google.api_core.grpc_helpers.create_channel\\(\n(\\s+)address,\n\\s+credentials=.*,\n\\s+scopes=.*,\n' in google/cloud/monitoring_v3/gapic/transports/group_service_grpc_transport.py. synthtool > Replaced 'return google.api_core.grpc_helpers.create_channel\\(\n(\\s+)address,\n\\s+credentials=.*,\n\\s+scopes=.*,\n' in google/cloud/monitoring_v3/gapic/transports/notification_channel_service_grpc_transport.py. synthtool > Replaced 'from google.cloud.monitoring_v3.gapic import notification_channel_service_client\n' in google/cloud/monitoring_v3/__init__.py. synthtool > Replaced 'notification_channel_service_client.NotificationChannelServiceClient' in google/cloud/monitoring_v3/__init__.py. synthtool > Cleaned up 1 temporary directories. 

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)