Introduce Quay integration

[gastaldi]

• Introduce Quay integration
• Update README.md

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.

Terraform Plan 📖success

Running plan in the remote backend. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

The remote workspace is configured to work with configuration at
terraform-scripts relative to the target repository.

Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/quarkiverse-devops/quarkiverse-devops/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
    /home/runner/work/quarkiverse-devops/quarkiverse-devops

To view this run in a browser, visit:
https://app.terraform.io/app/quarkiverse/quarkiverse-devops/runs/run-TJ57kr51k4dusk3Y

Waiting for the plan to start...

Terraform v1.9.7
on linux_amd64
Initializing plugins and modules...

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # quay_repository.quarkus_playpen will be created
  + resource "quay_repository" "quarkus_playpen" {
      + description = "Live local development on a deployed k8s service"
      + name        = "quarkus-playpen"
      + namespace   = "quarkiverse"
      + visibility  = "public"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Pusher: @gastaldi, Action: pull_request, Workflow: Terraform