End-user facing scripts should be easily identifiable

[glennmusa]

Benefit/Result/Outcome
When I clone the repo, I should fall into some predictable place to run the end-user automation

Description
Today, I can think of these scripts that are purpose-built for end users:

• src/deploy.sh
• src/clean.sh
• scripts/setup_ezdeploy.sh

and these scripts are referenced in docs and helpful:

• scripts/mlz_tf_setup.sh
• scripts/config/config_clean.sh
• scripts/setup_ezdeploy_local.sh
• scripts/init_terraform.sh
• scripts/apply_terraform.sh
• scripts/destroy_terraform.sh

Acceptance Criteria

• When I clone the repo, it's obvious to me what set of scripts get me started
• When I clone the repo, it's obvious to me what set of scripts are helpers/helpful, but not related to the internals of how MissionLZ works
• When I clone the repo, the internals of MissionLZ that I don't need to touch are obviously separate
• The purpose-built scripts for end users have clear names like deploy.sh, clean.sh, deploy_ui.sh