fix(ws): add secrets field to backend API schema

[andyatmiami]

related: #239

This commit brings partial support for secrets to the backend API. It enables the frontend component to successfully create a Workspace through the "wizard flow".

HOWEVER, it is important to note this secrets attribute is not supported within the controller component yet - as #240 is not yet merged. To unblock the frontend - the logic contained in this commit simply adds the necessary scaffolding to accept the secrets attribute defined within volumes. Once umarshalled, the backend essentially ignores this data. Code to fully enable the end to end flow is included in this PR - but simply commented out with TODO: comments denoting what can be uncommented once #240 is merged into notebooks-v2. A test is also presently disabled with XIt - and can also be enabled when required code present.

Changes were initially coded against the branch provided on #240 to verify full end-to-end behavior. Once confirmed, commit was rebased onto notebooks-v2, relevant code commented out as described above, and behavior retested to ensure desired outcome.

In summary, with these changes:

• backend API accepts volumes.secrets in the Create payload
• secrets data is NOT USED when programmatically constructing the Workspace CR
• Resultant workspace has no secrets data - irrespective of it if was provided in the payload or not.

[andyatmiami]

Functionality was verified by running the frontend component locally against a backend service (also local) containing the changes of this PR.

As evidenced in the following screenshot - the andy-test-pr-verify Workspace was able to be successfully created - and it included secrets information in the payload.

Furthermore, the Workspace CR that was created does NOT contain secrets information - as intended by the code at this time.

 $ kubectl get workspaces/andy-test-pr-verify -o json
{
    "apiVersion": "kubeflow.org/v1beta1",
    "kind": "Workspace",
    "metadata": {
        "creationTimestamp": "2025-05-13T19:29:05Z",
        "generation": 1,
        "name": "andy-test-pr-verify",
        "namespace": "default",
        "resourceVersion": "125717",
        "uid": "ee1fc290-b241-4703-8f19-1a3a48ced500"
    },
    "spec": {
        "deferUpdates": false,
        "kind": "jupyterlab",
        "paused": false,
        "podTemplate": {
            "options": {
                "imageConfig": "jupyterlab_scipy_190",
                "podConfig": "tiny_cpu"
            },
            "podMetadata": {},
            "volumes": {
                "data": [
                    {
                        "mountPath": "/data/my-data",
                        "pvcName": "workspace-data-pvc",
                        "readOnly": false
                    }
                ],
                "home": "workspace-home-pvc"
            }
        }
    },
    "status": {
        "activity": {
            "lastActivity": 0,
            "lastUpdate": 0
        },
        "pauseTime": 0,
        "pendingRestart": false,
        "podTemplateOptions": {
            "imageConfig": {
                "desired": "jupyterlab_scipy_190"
            },
            "podConfig": {
                "desired": "tiny_cpu"
            }
        },
        "podTemplatePod": {
            "containers": [
                {
                    "name": "main"
                }
            ],
            "name": "ws-andy-test-pr-verify-z5qfg-0"
        },
        "state": "Running",
        "stateMessage": "Workspace is running"
    }
}

[ederign]

/ok-to-test

[ederign]

@andyatmiami can you please fix the lint for this PR?

Also, I'm fine to merge this to unblock frontend. We just need to remember to update the open api definition later (we can do in a FUP PR).

[ederign]

Approving this to unblock FE. We will update this PR after secrets controller PR gets merged.

[ederign]

/approve

[ederign]

/ok-to-test

[thesuperzapper]

/approve
/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ederign, thesuperzapper

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thesuperzapper]

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