Attempting to configure monitoring fails if workspace host project differs from resource host
We generally recommend that a single Stackdriver workspace is configured per product and hosted in the meta project. This is setup we can do prior to any deployment as part of the product infrastructure bootstrap. (See, for example, the undergrad admissions project which does this.)
Currently this module cannot be used in such situations since the stackdriver workspace host project must match the project of the resources being monitored. Refactor this to allow separate workspace host projects.