Updated installer script for multiple fixes and features

[subdriven]

Description

Multiple fixes for the installer script including fixes noted below, added support for new Debian, Ubuntu, and Rocky Linux distributions as well as checks for now EOL or unsupported OSes. Refactored some of the script to fix logging and display issues.

Fixes # (issue)
Fixed #10581 installer does not work on CentOS7
Fixed #10105 php not found, composer failed
Fixed #9035 CentOS 7 IUS repos missing
Fixed #9844 Can't install on CentOS 8
Fixed #9724 Fresh install from installer gives permission error
Fixed #8750 Clean install using install script fails with error

(and probably some others)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Created a virtual machine of each OS, clean install with minimal default installations. Tested against every OS listed:

• CentOS 6 (EOL, script checks for this)
• CentOS 7
• CentOS 8
• CentOS 9
• Debian 9
• Debian 10
• Debian 11
• Fedora 36 (latest at time of testing)
• Rocky 8
• Rocky 9
• Ubuntu 14.04.6
• Ubuntu 18.04.6
• Ubuntu 20.04.5
• Ubuntu 21.10
• Ubuntu 22.04.1

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[snipe]

Why are we changing the case for distro names here? I'd expect that to potentially interfere with people's workflows if they're not expecting it. Ideally it would be case insensitive.

[subdriven]

Because the wording was used in notices to the user and was trying to make it look better. Easy enough to revert w/o causing issues.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉

[snipe]

Ack - that PR was merged into master. In the future, please always branch from develop and put your PR up against the develop branch, per the developer docs.

If the case-sensitivity ends up being an issue, we can always fix it if it's messing folks up.

Thanks for this!