support oci_uri as a remote data source for wasm

Title: One line description

Description:

Envoy only supports fetching a WASM module remotely via http

Majority of the WASM Modules now live in OCI Registries, so would be great if an oci field was supported to allow users to fetch WASM modules directly instead of using a shim (an auxiliary control plane creating a temporary file server or a sidecar agent that prefetches from an OCI registry and persists it into the common filesystem) that deals with the CRUD state machine

[optional Relevant Links:]

Any extra documentation required to understand the issue.

• OCIGetter in Helm (in Golang): https://github.com/helm/helm/blob/main/pkg/getter/ocigetter.go
• Istio's API for WASM https://istio.io/latest/docs/reference/config/proxy_extensions/wasm-plugin/