[Dogfooding] Create website deploy previews for PRs using odo deploy

[rm3l]

What type of PR is this:
/area testing

What does this PR do / why we need it:
This is a follow-up to the Dogfooding idea started with #6564
I wanted to take this opportunity to try odo as an outer-loop tool from a user perspective.
This PR adds a 'deploy' command to the website Devfile, and adds a GitHub Workflow that is triggered on PR events, and uses this Devfile to run odo deploy against our internal Kubernetes cluster, in order to create Deploy Previews for PRs (similar to what Netlify currently does).
Once a PR is open, a dedicated namespace is created, and odo deploy is run against it. If deployment is successful (and the preview URL is reachable), a comment with the preview URL is automatically added to the PR.
Once a PR is closed, the dedicated namespace is deleted.

NOTE: for security purposes, PRs from external forks will need a manual review and approval to be deployed (because this operation requires access to the GitHub Repository Secrets).

Examples of such PRs:

• test: some changes to the website (2) rm3l/odo#65
• [PR From Fork] Update index.tsx rm3l/odo#66 (from external fork)

Which issue(s) this PR fixes:
DevTools week idea.

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

How to test changes / Special notes to the reviewer:

• Locally:
  You should be able to run odo deploy from the docs/website folder.
  Note that this leverages the Image Name as selector feature to keep the Devfile portable. That is, the container image used in the image component is relative, and will be substituted in all matching components accordingly. For this to work, you need to set the ImageRegistry preference, e.g.:

# Make sure you are logged into the registry
# Set the ImageRegistry preference, e.g.:
$ odo preference set ImageRegistry quay.io/$USER

$ cd docs/website
$ odo deploy --var DEPLOY_INGRESS_DOMAIN=<ingressDomain, e.g.: 127.0.0.1.nip.io or ${minikubeIp}.nip.io>
# Access the URL accessible via the Ingress resource reported by this command:
$ odo describe component

• Once this PR is merged in, any PRs updating the website will be deployed into our test Kubernetes cluster, and a comment with the preview URL will be added to the PR.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[netlify]

🔨 Deploy Preview deleted from internal cluster!

Name	Link
🔨 Latest commit	0a3d2dc
😎 Deploy Preview	https://odo-dev-pr-6871.odo-test-kubernetes-clust-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/

[odo-robot]

Kubernetes Docs Tests on commit 63c8e27 finished with errors.
View logs: TXT HTML

[odo-robot]

NoCluster Tests on commit 128436b finished successfully.
View logs: TXT HTML

[odo-robot]

OpenShift Unauthenticated Tests on commit 128436b finished successfully.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit 128436b finished successfully.
View logs: TXT HTML

[odo-robot]

Validate Tests on commit 128436b finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit 128436b finished successfully.
View logs: TXT HTML

[odo-robot]

OpenShift Tests on commit 128436b finished with errors.
View logs: TXT HTML

[odo-robot]

Windows Tests (OCP) on commit 128436b finished successfully.
View logs: TXT HTML

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[rm3l]

 << Timeline

  [FAILED] registry_list_output.mdx
  Expected
      <string>: Â Â strings.Join({
      Â Â 	... // 106 identical bytes
      Â Â 	"                          VERSIONS\nnodejs-react  StagingRegistry",
      Â Â 	"         React is a free and open-source front-en...  2.0.2, 2.1",
      +Â 	".0, 2.2",
      Â Â 	".0\nnodejs-react  DefaultDevfileRegistry  React is a free and ope",
      Â Â 	"n-source front-en...  2.0.2, 2.1.0\n```\n",
      Â Â }, "")
      
  to be empty
  In [It] at: /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:189 @ 06/14/23 14:49:39.337
------------------------------
Spawning '/go/bin/odo delete project odo-dev' from /tmp/1520707937
•••Spawning '/go/bin/odo delete namespace odo-dev' from /tmp/2435076495
•

Summarizing 1 Failure:
  [FAIL] doc command reference odo init Non Interactive Mode fetching devfile from a registry when setting up the registry [It] Fetch Devfile from any registry of the list [nocluster]
  /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:189

Ran 16 of 16 Specs in 51.597 seconds
FAIL! -- 15 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestDocCommandReferenceAutomation (51.62s)
FAIL

Reported in #6876

/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

In response to this:

<< Timeline

 [FAILED] registry_list_output.mdx
 Expected
     <string>: Â Â strings.Join({
     Â Â 	... // 106 identical bytes
     Â Â 	"                          VERSIONS\nnodejs-react  StagingRegistry",
     Â Â 	"         React is a free and open-source front-en...  2.0.2, 2.1",
     +Â 	".0, 2.2",
     Â Â 	".0\nnodejs-react  DefaultDevfileRegistry  React is a free and ope",
     Â Â 	"n-source front-en...  2.0.2, 2.1.0\n```\n",
     Â Â }, "")
     
 to be empty
 In [It] at: /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:189 @ 06/14/23 14:49:39.337
------------------------------
Spawning '/go/bin/odo delete project odo-dev' from /tmp/1520707937
•••Spawning '/go/bin/odo delete namespace odo-dev' from /tmp/2435076495
•

Summarizing 1 Failure:
 [FAIL] doc command reference odo init Non Interactive Mode fetching devfile from a registry when setting up the registry [It] Fetch Devfile from any registry of the list [nocluster]
 /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:189

Ran 16 of 16 Specs in 51.597 seconds
FAIL! -- 15 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestDocCommandReferenceAutomation (51.62s)
FAIL

Reported in #6876

/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rm3l]

  [FAILED] Timed out after 420.001s.
  Expected
      <string>:   __
       /  \__     Developing using the "wowyom" Devfile
       \__/  \    Namespace: cmd-dev-test572nhi
       /  \__/    odo version: v3.11.0
       \__/
      
      ↪ Running on the cluster in Dev mode
       •  Waiting for Kubernetes resources  ...
       âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       âš   Pod is Pending
       âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
       âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[odo-projects odo-shared-data kube-api-access-8ddd6]: timed out waiting for the condition
       âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
       âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[kube-api-access-8ddd6 odo-projects odo-shared-data]: timed out waiting for the condition
       âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
      
  to contain substring
      <string>: [Ctrl+c] - Exit
  In [BeforeEach] at: /go/odo_1/tests/helper/helper_run.go:54 @ 06/14/23 14:49:51.081
------------------------------
•

Summarizing 1 Failure:
  [FAIL] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when stopping odo dev normally should have deleted all resources before returning
  /go/odo_1/tests/helper/helper_run.go:54

Ran 501 of 950 Specs in 1645.979 seconds
FAIL! -- 500 Passed | 1 Failed | 0 Pending | 449 Skipped

Not related - issue reported in #6894

/override OpenShift-Integration-tests/OpenShift-Integration-tests

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests

In response to this:

 [FAILED] Timed out after 420.001s.
 Expected
     <string>:   __
      /  \__     Developing using the "wowyom" Devfile
      \__/  \    Namespace: cmd-dev-test572nhi
      /  \__/    odo version: v3.11.0
      \__/
     
     ↪ Running on the cluster in Dev mode
      •  Waiting for Kubernetes resources  ...
      âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
      âš   Pod is Pending
      âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
      âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
      âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[odo-projects odo-shared-data kube-api-access-8ddd6]: timed out waiting for the condition
      âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
      âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[kube-api-access-8ddd6 odo-projects odo-shared-data]: timed out waiting for the condition
      âš   AttachVolume.Attach failed for volume "pvc-b8a36807-f40e-46d4-afd2-0b6cead142c7" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-572467ca-20c8-4427-afb0-4e3e823f9268
     
 to contain substring
     <string>: [Ctrl+c] - Exit
 In [BeforeEach] at: /go/odo_1/tests/helper/helper_run.go:54 @ 06/14/23 14:49:51.081
------------------------------
•

Summarizing 1 Failure:
 [FAIL] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when stopping odo dev normally should have deleted all resources before returning
 /go/odo_1/tests/helper/helper_run.go:54

Ran 501 of 950 Specs in 1645.979 seconds
FAIL! -- 500 Passed | 1 Failed | 0 Pending | 449 Skipped

Not related - issue reported in #6894

/override OpenShift-Integration-tests/OpenShift-Integration-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rm3l]

/test odo-ocp4.13-lp-interop-images
/test odo-ocp4.14-lp-interop-images