Feat- Add role for managing SSH host keys

See merge request !129

fix: update cluster hook playbook name

See merge request !132

Feat remove resource autocreation

See merge request !130

fix: change variable for enable proxy build

See merge request !131

- Ensure the `/tmp/ssh_keys` directory exists.
- Download SSH host keys from S3 and unpack them to `/etc/ssh`.
- Restart the SSH service to apply the new keys.
- Add necessary variables for S3 and AWS credentials in `groupvars/all`.
- Include `ssh_host_keys` role in `cluster.yml` playbook.

feat: deploy environment as variable

See merge request !126

fix: dhclient.conf not exist

See merge request !127

Feat pkr tmpl proxy almalinux

See merge request !124

Many EPEL packages require the CodeReady Builder (CRB) repository
It is recommended that you run /usr/bin/crb enable to enable the
CRB repository.

fix: move cluster.yml to correct location

See merge request !125

Feat individual build

See merge request !119

Rename cheaha.yml playbook to cluster.yml

See merge request !116

Rename it because cheaha is not the only cluster we deploy against. So
give it a generic name.

Add a task to template DNS config

See merge request !115

This will allow you to define the variables during runtime whose values
you may want to override. In this case, we want to override the DNS
config related to nameserver and search domain

Mount dirs besides adding them to fstab

See merge request !114

Otherwise, since we run this role in deploy the dirs won't be mounted
and cause unexpected behavior of applications.

Create multi homed proxy

See merge request !111

removed dev_key to move var to gitlab pipeline variable

See merge request !113

Avoids error that the IP has already been assigned while trying multiple
proxy deploys

The instance creation with internal port attached was causing issues
with login because the default gateway was set to internal network
gateway. This will only allow login via headnode but not the host.
This commit will fix that issue by giving a way to define the gw ip
for default route.

We wanted to create a multi-homed instance connected to proxy-net and
internal-net because the nfs-mounts are shared via internal net by the server.
However, the NIC on internal-net wasn’t getting an IP assigned automatically
and this was creating an issue for NFS server to communicate with the clients.
So we created a port and assigned that port during instance creation