Bug 2064696

Description of problem:
When applying the ansible or bash remediation for rule:

http://static.open-scap.org/ssg-guides/ssg-rhel8-guide-stig.html#xccdf_org.ssgproject.content_rule_configure_tmux_lock_after_time

The file /etc/tmux.conf has permissions 600 for root user because of a previous rule.


- From ansible doc:
---
If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.
---

- And we can see in the same STIG guide (http://static.open-scap.org/ssg-guides/ssg-rhel8-guide-stig.html#!) that umask must be set to 077:
---
Ensure that Users Have Sensible Umask Values   Group contains 5 rules
Group   Ensure that Users Have Sensible Umask Values   Group contains 5 rules http://static.open-scap.org/ssg-guides/ssg-rhel8-guide-stig.html#xccdf_org.ssgproject.content_group_user_umask
---

Then all normal user will have a message "/etc/tmux.conf: Permission denied" and 'stuck' for 2.5 minutes when login.

Version-Release number of selected component (if applicable):
RHEL 8.5

How reproducible:
Always

Steps to Reproduce:
1. apply stig ansible role https://github.com/RedHatOfficial/ansible-role-rhel8-stig
2. login with non root user
3. 

Actual results:
- /etc/tmux.conf with wrong permissions
- Message "/etc/tmux.conf: Permission denied" with delay to have the prompt

Expected results:
- right permissions and no delay to login

Additional info: