[Feature]: Helm: optional OASF-SDK extractor server deployment + config

[akijakya]

Problem Statement

The directory Helm chart has no extractor. In the cloud we want an OASF-SDK gRPC server deployed alongside the directory, with the gateway pointed at it. The OASF-SDK repo already publishes a Helm chart + image, so this is wiring, not building a service.

Proposed Solution

• Add oasf-sdk as an optional subchart dependency of the apiserver chart (oci://ghcr.io/agntcy/oasf-sdk/helm-charts), gated condition: oasfSdk.enabled, mirroring the existing optional oasf (schema-server) subchart.
• Default oasfSdk.enabled: false (local uses provisioned assets); the prod gitops values.yaml flips it true.
• Set the apiserver Deployment's extractor.remoteAddr to the OASF-SDK service DNS when enabled.
• Document enabling it in the gitops prod values (the deployment repo).

Acceptance criteria

• helm template with oasfSdk.enabled=true renders the OASF-SDK Deployment/Service and points extractor.remoteAddr at it.
• Default render (false) is unchanged from today.
• README/values documented.

Depends on the extractor config + daemon/gateway wiring issue. Needed by the remote-mode e2e.