[TASK] Migrate JWA test-related workflows from kubeflow/kubeflow to notebooks-v1 branch

[andyatmiami]

Certification

• I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

This task involves migrating all existing testing GitHub Actions workflows for Jupyter Web App (JWA) from kubeflow/kubeflow to kubeflow/notebooks repository. The goal is to establish feature parity within kubeflow/notebooks notebooks-v1 branch w.r.t the checks ran against code contributions.

The following workflows should be migrated as part of this work:

• jwa_integration_test.yaml
• jwa_multi_arch_test.yaml
• jwa_frontend_tests.yaml
• jwa_backend_unittests.yaml

Majority of logic should be able to remain as-is... however, particular attention should be paid to:

• any ghcr.io container registry reference
  • see: [TASK] Define first release artifacts and branches for notebooks-v1 #583
• dependencies on components/common
  • see: [TASK] Agree on future of components/common in notebooks-v1 #584

Acceptance Criteria

• jwa_integration_test.yaml runs on kubeflow/notebooks notebooks-v1 branch in a manner consistent with how it ran on kubeflow/kubeflow
• jwa_multi_arch_test.yaml runs on kubeflow/notebooks notebooks-v1 branch in a manner consistent with how it ran on kubeflow/kubeflow
• jwa_frontend_tests.yaml runs on kubeflow/notebooks notebooks-v1 branch in a manner consistent with how it ran on kubeflow/kubeflow
• jwa_backend_unittests.yaml runs on kubeflow/notebooks notebooks-v1 branch in a manner consistent with how it ran on kubeflow/kubeflow

[andyatmiami]

/area v1

[yehudit1987]

/assign