Fix slurm-client role failing because of munge-key not being copied during the deploy

We were not running the slurm-client role that installs slurm packages. When I tried to run it I got an error

TASK [slurm_client : Copy munge key] *******************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "Could not find or access 'munge.key'\nSearched in:\n\t/tmp/hpc-factory/ansible/roles/slurm_client/files/munge.key\n\t/tmp/hpc-factory/ansible/roles/slurm_client/munge.key\n\t/tmp/hpc-factory/ansible/roles/slurm_client/tasks/files/munge.key\n\t/tmp/hpc-factory/ansible/roles/slurm_client/tasks/munge.key\n\t/tmp/hpc-factory/ansible/files/munge.key\n\t/tmp/hpc-factory/ansible/munge.key on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}

Ansible could not find the munge key because we download it from the s3. Its done before the user-data section so it is on the runner. Previously it was not an issue because we ran this role during the build Fixing it