CDK post-deployment experience

## Description

We want to support operators of CDK applications during their common tasks. What are the biggest problems/frustrations you would like us to address?

* Getting an overview of the application?
* Creating dashboards and alarms?
* Ticketing?
* Operational tasks?
* Log inspection?

Let us know in the discussion below.

## Roles

| Role | User
|---------------------|------------------------------
| Proposed by | @rix0rrr
| Author(s) |
| API Bar Raiser |
| Stakeholders |

> See [RFC Process](https://github.com/aws/aws-cdk-rfcs#rfc-process) for details

## Workflow

- [x] Tracking issue created (label: `status/proposed`)
- [ ] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) if needed)
- [ ] Kick off meeting
- [ ] RFC pull request submitted (label: `status/review`)
- [ ] Community reach out (via Slack and/or Twitter)
- [ ] API signed-off (label `api-approved` applied to pull request)
- [ ] Final comments period (label: `status/final-comments-period`)
- [ ] Approved and merged (label: `status/approved`)
- [ ] Execution plan submitted (label: `status/planning`)
- [ ] Plan approved and merged (label: `status/implementing`)
- [ ] Implementation complete (label: `status/done`)

---

> Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

Start with the discussion on issue #437 and review the linked RFC Process to understand how this proposal is expected to progress. Done would require turning the open-ended operator frustrations into a concrete, agreed RFC with an execution plan; no implementation files or tests are identified.

Written by the indexing model from the issue text.