[ECR] [request]: Exclude kernel-related CVEs from container scan results

### 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**
Already mentioned at https://github.com/aws/containers-roadmap/issues/798#issuecomment-623847952 but not yet resolved. Currently, the AWS Inspector container scan results display Linux kernel vulnerabilities, even though the container is running on top of the host kernel, which is not dependent on the container image. Therefore, these entries in the results are false positives, or something that we can't affect, and should be excluded to reduce noise.

**Which service(s) is this request for?**
ECR

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Problem is too much unnecessary noise in scan results. Goal is to reduce it.

**Are you currently working around this issue?**
No

**Additional context**
No

**Attachments**
No

No repository files, tests, or implementation entry points are identified; this is a request for AWS Inspector/ECR behavior. Start by reviewing the related containers-roadmap issue and the current scan-result documentation. Done means kernel-related CVEs are excluded from ECR container scan results without hiding vulnerabilities relevant to the image.

Written by the indexing model from the issue text.