[ECS] [request]: Improved Service Update Notifications

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
We recently received a "Service Update Notification" stating that several of our ECS tasks need to be restarted. We typically segment our environments by cluster and use the same service names across all environments. It would be great if the Service Update Notification also included the ECS Cluster Name for each affected service.

We opened an AWS Support ticket and they directed us to the Personal Health Dashboard, which also only shows the Service Name, and lacks the Cluster Names. Additionally, the Personal Health Dashboard provides the information under the "Other Notifications" section, instead of "Scheduled Changes" where it probably should be, considering that AWS will be restarting services on our behalf. If the notification could be under "Scheduled Changes" and could also be kept up-to-date, it would be easy for engineers to restart some services ahead of time and always be aware of what services (if any) are remaining.

**Which service(s) is this request for?**
This request is for ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I'm trying to determine which services (if any) I need to restart ahead of the mandatory Fargate task relaunch. We use the same task/service names across environments, and the notification didn't include any Cluster information, so it is impossible to determine exactly which services are the ones affected.

**Are you currently working around this issue?**
Opened an AWS support ticket and learned that all services that were started before a particular date are affected. Manually maintaining a list of services that are left to be restarted.

**Additional context**
Unless creating a task against the default ECS cluster, users must provide ECS Cluster name for all AWS ECS CLI/API commands (including even listing tasks/services), so this seems a rather sizable gap in the notification.

**Attachments**
N/A.

The request concerns AWS ECS Service Update Notifications and the Personal Health Dashboard; no repository files, tests, or implementation entry points are identified. Start by reviewing the notification requirements in the issue. Done means affected services include their ECS cluster names, appear under Scheduled Changes, and remain up to date.

Written by the indexing model from the issue text.