**Apache Airflow version**: 1.10.12

**Kubernetes version** : 1.17.9

**Environment**:

- **Cloud provider or hardware configuration**: Azure Kubernetes Service
- **OS** (e.g. from /etc/os-release): Linux
- **Install tools**: Helm chart (/chart in repo) 
- **Others**:

**What happened**:
Pod cannot run since `airflow-cleanup-pods` is not in $PATH
```
Error: failed to start container "airflow-cleanup-pods": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"airflow-cleanup-pods\": executable file not found in $PATH": unknown
```

**What you expected to happen**: 
Cleanup job pod runs

<!-- What do you think went wrong? -->

**How to reproduce it**:
* Deploy Helm Chart
* Manually trigger `airflow-cleanup ` CronJob 
* See it cannot run since `airflow-cleanup-pods` is not in $PATH
airflow/cli/cli_parser.py
"Run subsections of a DAG for a specified date range. If reset_dag_run option is used, "
            "backfill will first prompt users whether airflow should clear all the previous dag_run and "
            "task_instances within the backfill date range. If rerun_failed_tasks is used, backfill "
            "will auto re-run the previous failed task instances  within the backfill date range"
        ),
        func=lazy_load_command('airflow.cli.commands.dag_command.dag_backfill'),
        args=(
            ARG_DAG_ID, ARG_TASK_REGEX, ARG_START_DATE, ARG_END_DATE, ARG_MARK_SUCCESS, ARG_LOCAL,
            ARG_DONOT_PICKLE, ARG_YES, ARG_BF_IGNORE_DEPENDENCIES, ARG_BF_IGNORE_FIRST_DEPENDS_ON_PAST,
            ARG_SUBDIR, ARG_POOL, ARG_DELAY_ON_LIMIT, ARG_DRY_RUN, ARG_VERBOSE, ARG_CONF,
            ARG_RESET_DAG_RUN, ARG_RERUN_FAILED_TASKS, ARG_RUN_BACKWARDS
        ),
    ),
    ActionCommand(
        name='test',
        help="Execute one single DagRun",
        description=("Execute one single DagRun for a given DAG and execution date, "
                     "using the DebugExecutor.\n"
                     "\n"
                     "The --imgcat-dagrun option only works in iTerm.\n"
                     "\n"
                     "For more information, see: https://www.iterm2.com/documentation-images.html\n"
                     "\n"
                     "If --save-dagrun is used, then, after completing the backfill, saves the diagram "
                     "for current DAG Run to the indicated file.\n"
                     "The file format is determined by the file extension. "
                     "For more information about supported format, "
                     "see: https://www.graphviz.org/doc/info/output.html\n"
                     "\n"
                     "If you want to create a PNG file then you should execute the following command:\n"