chore: ensure init-deployment.sh works when invoked using sudo

Recent testing of the cookiecutter deployment template surfaced a bug in the validate_python_cmd
function of the init-deployment.sh script. The command that checks that the jinja2 library was
installed would break when you ran init-deployment.sh using the `--python` option in tandem with
sudo. The root cause was that the way the command is quoted before it is passed to `python -c` was
not compatible with all bash invocation modes. This commit fixes the function to be broadly
compatible.

Author: jkglasbrenner

cookiecutter-templates/cookiecutter-dioptra-deployment/{{cookiecutter.__project_slug}}/init-deployment.sh

@@ -142,17 +142,25 @@ log_info() {
 ###########################################################################################
 
 validate_python_cmd() {
-  local python_cmd="${1}"
+  local candidate_python_cmd="${1}"
 
-  if ! command -v "${python_cmd}" >/dev/null 2>&1; then
-    log_error "Command ${python_cmd} not found, exiting..."
+  if ! command -v "${candidate_python_cmd}" >/dev/null 2>&1; then
+    log_error "Command \"${candidate_python_cmd}\" not found, exiting..."
     exit 1
   fi
 
   local jinja2_installed
-  local jinja2_cmd_check="'import importlib.util;print(importlib.util.find_spec("jinja2") is not None)'"
-  if ! jinja2_installed="$(${python_cmd} -c ${jinja2_cmd_check})"; then
-    log_error "Command ${python_cmd} -c ${jinja2_cmd_check} failed, exiting..."
+  local jinja2_cmd_check=(
+    "import"
+    "importlib.util;"
+    'print(importlib.util.find_spec("jinja2")'
+    "is"
+    "not"
+    "None)"
+  )
+  if ! jinja2_installed="$("${candidate_python_cmd}" -c "${jinja2_cmd_check[*]}")"; then
+    log_error "Command \"${candidate_python_cmd}\" -c \"${jinja2_cmd_check[*]}\"" \
+      "failed, exiting..."
     exit 1
   fi