feature: OpenAPIv3 support in virtual workspace framework

[embik]

Feature Description

Virtual workspaces act as "virtual" Kubernetes-like API endpoints, but they do not support OpenAPI to discover API schemas. This makes virtual workspaces not feel like a "fully fledged" endpoint, and especially if users interact with kcp through virtual workspaces they might be missing the usual ergonomics of interacting with a Kubernetes API (e.g. kubectl explain won't work).

It would therefore be nice if OpenAPIv3 information was exposed by virtual workspaces.

Proposed Solution

An initial solution was sketched out in #3059. The virtual workspace framework should be capable of generating and updating OpenAPIv3 information and serve it.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response