instance.namespace is not one of enum values: amunozhe,cmoullia,demo,iocanel",

[cmoulliard]

Issue

e2e job fails to scaffold a project

{
  "errors": [
    {
      "path": [
        "namespace"
      ],
      "property": "instance.namespace",
      "message": "is not one of enum values: amunozhe,cmoullia,demo,iocanel",
      "schema": {
        "title": "Namespace",
        "type": "string",
        "description": "The openshift/kubernetes namespace for deploying resources",
        "default": "demo",
        "enum": [
          "amunozhe",
          "cmoullia",
          "demo",
          "iocanel"
        ]
      },
      "instance": "dummy",
      "name": "enum",
      "argument": [
        "amunozhe",
        "cmoullia",
        "demo",
        "iocanel"
      ],
      "stack": "instance.namespace is not one of enum values: amunozhe,cmoullia,demo,iocanel"
    },
    {
      "path": [
        "virtualMachineNamespace"
      ],
      "property": "instance.virtualMachineNamespace",
      "message": "is not one of enum values: amunozhe,cmoullia,demo,iocanel",
      "schema": {
        "title": "VMI Namespace",
        "description": "Namespace where the virtual machine runs",
        "type": "string",
        "default": "demo",
        "enum": [
          "amunozhe",
          "cmoullia",
          "demo",
          "iocanel"
        ]
      },
      "instance": "dummy",
      "name": "enum",
      "argument": [
        "amunozhe",
        "cmoullia",
        "demo",
        "iocanel"
      ],
      "stack": "instance.virtualMachineNamespace is not one of enum values: amunozhe,cmoullia,demo,iocanel"
    }
  ]
}

[cmoulliard]

As the dummy namespace don't exist within the backstage template enum list but instead demo, we will change it to use foe the e2e job the namespace: demo. The argocd application.namespaces will also be changed to allow to access the demon namespace instead of dummy