Closes #181

Defining a network can be optional when a port is already defined when
deploying a VM.

This commit adds flexibility where you can either use --port or
--network options to define a network during the deployment.

Alternatively, you can define both but the port cannot be from the same
network you used in the --network option. Otherwise, you will have two
ips from the same network which will cause network reachability issues.

Enable rsyslog configuration by default

See merge request !183

fix: restart firewalld only when it was running

See merge request !188

fix: restart firewalld after change

See merge request rc/hpc-factory!187

fix node exporter with firewalld enabled

See merge request !186

feat: Add a way to define multiple security groups

See merge request !176

Add node exporter

See merge request rc/hpc-factory!184

Changed the 'enable_rsyslog_config' variable from false to true
This should be the default behavior for all nodes unless explicitly turned off by the developer.

feat: disable fail2ban by default

See merge request !180

Install and configure fail2ban

See merge request rc/hpc-factory!178

Adds fail2ban filter and jail configs

Add symbolic links for Slurm config files

See merge request rc/hpc-factory!177

Feat build extra vars

See merge request !168

Created symlinks for `slurm.conf`, `gres.conf`, `slurmdbd.conf`, and `cgroup.conf` in `/etc/slurm`.
To ensure consistency with the current production environment where these symlinks already exist.

Closes #203

feat: update account app port

See merge request !174

Restart httpd service after update

See merge request !172

Update Apache configuration for OOD rewrite rules during deploy phase

See merge request !170

previously it reflected a placeholder but it actually is the value in file from build that we're looking for and replacing in deploy phase

We lookup the value of the placeholder (RewriteCond %{HTTP:REMOTE_USER}  \’^(.+)$\’) in this case in the apache conf during build and replace it with the rewrite conditions during deploy phase.

fix: Skip creating home dir for slurm user

See merge request !166

The home dir for slurm user is available as a mount from master so there
is no need to create a local home dir for it.