Fix injecting environment.yaml into citool-config volume

This is currently broken in production - environment.yaml does not exist there. Added a condition if the file exists and using an another approach - copying to the citool-config volume instead mounting it to a specific location. Citool-config can reference it directly, no need to update rules-engine options in the script anymore. See also ranch-public!11, it contains the placeholder environment.yaml which is being replaced.