git based deployment versioning and other deploy.sh improvements

[mreeve-snl]

🗣 Description

• Adds git control into LME's version process

  • testing variable: FORCE_LATEST_VERSION, can be set so a specific version can be passed in the environment during testing:
    • TO TEST upgrading:

    export FORCE_LATEST_VERSION="1.2.0"
    sudo -E ./deploy.sh install
    sudo -E ./deploy.sh upgrade
    

    • To Test Clean Install:

    export FORCE_LATEST_VERSION="1.3.0"
    sudo -E ./deploy.sh install
    

  • checkout LME directory to latest version

• fixes "bug" in deploy.sh:

  • makes it so that the permissions of Chapter\ 3\ Files directory are preseserved!

• upgrade function with 1.2.0 -> 1.3.0, upgrade path

• adds various features to deploy.sh:

  • makes logging wrappers
  • better prompt on install
  • ready check, to confirm user is ok with an action before proceeding
  • Checks for required packages during run of deploy.sh. SHould help if we ever add a package later to the deployment script

💭 Motivation and context

LME versioning should be tracked automatically via git and the installed version should be automatically tracked via git.
There was a little QOL of changes need for deploy.sh as well.

Solves: #69

🧪 Testing

Tested on a clean install of 1.2.0 -> upgrade 1.3.0
tested on a clean install of 1.3.0 on this branch

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated
  to reflect the changes in this PR.
• All new and existing tests pass.

[mreeve-snl]

I'll comment here when this is ready

[mreeve-snl]

When we're testing this, we'll want to use the following command:

export FORCE_LATEST_VERSION=1.3.0

that way the version set in lme.conf will be appropriate and expected.

[mreeve-snl]

OK release is ready for testing/approval!

[mitchelbaker-cisa]

Upgraded to latest version and ran clean install.