Update OLMv0 lifecycle enhancement to use ExperimentalListPackageCustomSchemas gRPC endpoint

[perdasilva]

Summary

• Update all references from ListPackageCustomSchemas to ExperimentalListPackageCustomSchemas to match the actual operator-registry implementation
• The endpoint lives on a new ExperimentalRegistry gRPC service, separate from the existing Registry service
• Document the x-acknowledge-experimental: true gRPC metadata header requirement — without it, the endpoint silently returns an empty stream
• Update input validation details to use the actual regex pattern (^[a-zA-Z0-9][a-zA-Z0-9._-]*$)
• Correct pogreb storage format: blobs stored under a single metas/{schema}/{packageName} key as concatenated length-prefixed proto binary (not per-hash keys with prefix scan)
• Update Console backend to include the experimental header in gRPC calls
• Update test plan to cover missing experimental header behavior

Test plan

• Enhancement document uses ExperimentalListPackageCustomSchemas consistently (no stale ListPackageCustomSchemas references)
• API Extensions section accurately describes the ExperimentalRegistry service, header requirement, and validation
• Implementation Details match the actual operator-registry code
• Console Backend section includes experimental header in gRPC call description
• Test plan covers experimental header behavior

🤖 Generated with Claude Code

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign stleerh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fgiudici]

Looks good here

[fgiudici]

nit: why don't we keep this? 🤔

[perdasilva]

I think I removed to not cause confusion about who is adding the lifecycle metadata for this work. In our case, the lifecycle metadata is owned by another actor our of band of the operator authors (of course there's nothing stopping the operator author from doing so).

[openshift-ci]

@perdasilva: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.