Move UX Portal internal app to public STACKIT

[larsrickert]

Why?

Similar to #4271, see description there.

Acceptance criteria

• the UX Portal application is moved from the internal network to the public STACKIT
• the database is moved from the internal network to the public STACKIT. NO DATA MUST BE LOST!
• after the applications are moved to the public STACKIT, the internal apps are shut down
• there is NO downtime of the application or it not possible otherwise it is communicated with the UX team!

Implementation details

• we can re-use the existing pipeline template for the OAuth proxy from the Vue Blueprint since the Blueprint and the UX Portal repository are in the same Azure organization:
• it might be necessary to create a new ODJ product to get a public STACKIT project

pool:
  vmImage: ubuntu-latest

resources:
  repositories:
    - repository: templates
      type: git
      ref: refs/heads/master
      name: schwarzit.odj-pipeline-templates/odj-deliver-templates
    - repository: blueprint-templates
      type: git
      ref: refs/heads/main
      name: schwarzit.odj.enterprise-blueprints/vue-blueprint

variables:
  - name: cf_service_connection
    value: stackit-cloudfoundry-prod
  - name: cf_org
    value: onyx

extends:
  template: templates/technologies/pnpm/v2/odj-pipeline-template-technology-pnpm.yml@templates
    custom_deploy_stages:
      - stage: Deploy
        condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/main'))
        jobs:
          - template: .azuredevops/pipelines/templates/cf-oauth-proxy/v1.yml@blueprint-templates
            parameters:
              service_connection: $(cf_service_connection)
              org: $(cf_org)
              space: prod
              app_route: ux-portal.schwarz
              app_base_name: ux-portal
              working_directory: $(Pipeline.Workspace)

DEV handover checklist

Storybook

DEV handover done with: @ADD_DEV_NAME_HERE

Testing

• covered by visual screenshot tests
• covered by functional tests (Playwright or unit test)

Documentation

• "New" badge in Storybook is added, see storybook-addon-tag-badges
• auto-generated Storybook code snippets are checked
• component status has been updated in the docs overview
• updated version is released
• updated documentation is deployed

Other

• follow-up tickets were created if necessary (add links below)