Improve UX for resources shared across multiple CLI projects

Some customers have multiple CLI projects to segment their checks. For example, a customer monitoring Product A, B, and C might create a CLI project for each (if they’re in separate repos, they want to deploy them separately, etc.)

However, these separate projects might use the same alert channels or status page. Our options now are not ideal:

• Deploy the shared resources via a separate CLI project. Then, use fromId() in each project to refer to the shared resources. This is the best option, but it can be cumbersome since we need to deploy the shared resources, grab the IDs for any that were created, plug them into the other projects, then deploy those.

• Create and manage them entirely from the website UI. Then, use fromId() in each project to refer to the shared resources. Not great, ideally all resources should be managed via the CLI.

• Re-create the shared resources in each project and accept the duplication. This is not ideal and makes it hard to keep those shared resources consistent. It’s also not plausible for something like a shared status page.