Add support for AlmaLinux 8/9 and Rocky Linux 8

[arvindshmicrosoft]

• Add support for AlmaLinux and Rocky Linux in the Ansible playbooks.
• Switch the default Azure VM image to AlmaLinux 9.
• Add an Azure-specific cloud-init file for AlmaLinux 9 to install rsync at first boot, as the image does not seem to install it.
• Add an Ansible task to stop and disable firewalld for AlmaLinux 9, to allow RPC communication within the cluster.
• Use Python to install Ansible on the proxy for non-CentOS OS to ensure a current version of Ansible is used. This avoids problems when the Ansible package in the EL repo is outdated or requires a newer Python than is supported by the given OS.
• While using Rocky Linux 9 is not blocked, there are some external issues with the Azure Linux agent and this OS version.
• These changes have been tested on Azure with various OS images used for the cluster nodes and the "proxy". Currently "known good" OS versions for Azure include Fedora 39, CentOS 7.9, AlmaLinux 8/9, Rocky Linux 8.
• Update references to CentOS 7 in the context of EC2 as the default image for EC2 had already been changed to a Fedora 35 AMI.

[ctubbsii]

@arvindshmicrosoft I think these changes are fine, as well as your others that you've recently submitted.

But, I'm wondering what the motivation is for these. As far as I can tell, the Fluo and Accumulo developers, who are the target audience for this project, aren't really using Muchos to do a lot of testing. I could be wrong about that, but it seems like the existence of a utility like Terraform supersedes the need for us to maintain this project. The Accumulo devs even maintain a set of Terraform templates/configs for testing in https://github.com/apache/accumulo-testing/tree/main/contrib/terraform-testing-infrastructure

Given the availability of Terraform and similar tools, is there really a strong need to continue to maintain Muchos, as you've been doing?
I'm asking the question in reply here because I'm not sure if you're following the mailing list right now, but feel free to respond on the Fluo dev mailing list instead of here to discuss, so as not to further hijack your PR with a tangentially related discussion.

[arvindshmicrosoft]

Thanks @ctubbsii the intention here was to get this project to a known good state, nothing more. I don't have any plans to add anything else to Muchos. Thanks for your time reviewing the PRs.