chore: update dependabot config and auto-merge

[tommartensen]

To prevent comments like #1654 (comment)

Assignees

The following users could not be added as assignees: stackrox/infra. Either the username does not exist or it does not > have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

Removing the assignees field, as it does not support teams as assignees.
Also adding the default labels again for the package managers where we have auto-merge.
Also adding @rhacs-bot as code owner to allow auto-merges to succeed and not be blocked by infra team review.

[rhacs-bot]

A single node development cluster (infra-pr-1677) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1677 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f