[Lambda][ECR]: improved integration

### 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**
AWS Lambda supports container images but does not integrate well with Amazon ECR. Several areas of improvement could enhance the user experience and streamline workflows:

1. **Image URI Navigation**: In the Lambda console's image section, the "Image URI" link redirects to the ECR registry instead of directly to the specific container image. To view the container image, users must click the link, then manually copy and paste the image ID from the "Resolved Image URI." A direct link to the specific image would simplify this process.

2. **Vulnerability Scanning Visibility**: ECR provides vulnerability scanning for container images, but the results are not visible in the Lambda console. It would be beneficial to display vulnerability scan results directly in the Lambda console. Additionally, a dedicated page listing all images used by Lambda functions, along with a summary of vulnerabilities, would be a valuable addition.

3. **Linking Lambda Functions to ECR Images**: When viewing an image in ECR, there is no indication of which Lambda function(s) are associated with that image. Adding this linkage would improve traceability and management.

4. **Orphaned Images Management**: Publishing a new image to a Lambda function can leave older images orphaned. Currently, there is no straightforward way to identify and manage orphaned images. These unused images can incur unnecessary costs if not removed. A feature to list orphaned images and facilitate their cleanup would be highly useful.

**Which service(s) is this request for?**
AWS Lambda and Amazon ECR

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Managing container images linked to Lambda functions is currently cumbersome due to the lack of integration between Lambda and ECR. Specifically:
- Navigating to container images linked to Lambda functions requires multiple manual steps.
- Vulnerability scan results for images are not easily accessible in the Lambda console.
- There is no way to trace Lambda functions back to their associated ECR images.
- Identifying and cleaning up orphaned images is a manual and time-consuming process, as ECR does not support tagging or automated cleanup.

**Are you currently working around this issue?**
To address these issues, I use a custom script that:
- Lists all Lambda functions and ECS tasks.
- Cross-references these with ECR images.
- Deletes or archives images that are not linked to Lambda functions or ECS tasks.

**Additional context**
N/A

**Attachments**
N/A

Issue nêu bốn khu vực tích hợp Lambda và ECR riêng biệt nhưng không cung cấp các tệp repository, kiểm thử hoặc entry point. Hãy bắt đầu bằng việc xác nhận với các maintainer xem khu vực cụ thể nào và phần bề mặt repository nào nằm trong phạm vi. Done nên được định nghĩa là một cải thiện tập trung, có thể kiểm thử, thay vì toàn bộ đề xuất tích hợp.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.