[Lambda] Support pulling container images via OCI index platform-specific digest lookup

### 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**
Support pulling container images via OCI index platform-specific digest lookup.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Recent versions of Docker buildx default to enabling provenance which causes an OCI index to be created with the specified image tag pointing to untagged image(s).
However, AWS Lambda does not support pulling the image by looking up the image via its platform-specific digest in that OCI index.

Error message:
```
The image manifest, config or layer media type for the source image is not supported. (Service: Lambda, Status Code: 400, Request ID: ) (SDK Attempt Count: 1)"
```

**Are you currently working around this issue?**
By disabling provenance during image builds.

**Additional context**
Registry is AWS ECR.

**Attachments**
None.

Das Issue nennt AWS Lambda, AWS ECR, Docker buildx und OCI indexes, enthält aber keine Repository-Dateien, Tests oder Einstiegspunkte. Beginne damit, das im Issue beschriebene Verhalten von Lambda-Container-Images und OCI indexes zu überprüfen; abgeschlossen ist die Aufgabe, wenn Lambda den plattformspezifischen Digest aus dem Index abrufen kann, ohne Provenance zu deaktivieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.