Requests made by path for "WEB_COMPUTE" platform

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

NA

### AWS Region

us-east-1

### Amplify Hosting feature

Access logs, CloudWatch metrics

### Is your feature request related to a problem? Please describe:

1. For WEB_DYNAMIC when resources deployed in our account. We could check the most requested paths from CF distribution using [popular-objects](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/popular-objects-report.html).

2. For WEB_COMPUTE resources deployed and managed in Amplify account. Access logs and Hosting compute logs contain logs for particular request but we can not check number of requests being made to a particular path.

### Describe how you'd like this feature to work

- Cloud Watch Metric for for tracking request by path.
- I found blogs which talks about some process but it's not ideal solution.
- [analyzing-aws-amplify-access-logs-part-1](https://www.outcoldman.com/en/archive/2021/01/14/analyzing-aws-amplify-access-logs-part-1/)
- [analyzing-aws-amplify-access-logs-part-2](https://www.outcoldman.com/en/archive/2021/02/04/analyzing-aws-amplify-access-logs-part-2/)

The issue concerns AWS Amplify WEB_COMPUTE access logs, Hosting compute logs, and CloudWatch metrics, but names no implementation file or test. Start by reviewing FAQ.md and CONTRIBUTING.md, then identify the access-log and metrics entry points. Done would require an agreed design and request counts by path for WEB_COMPUTE resources.

Written by the indexing model from the issue text.