fix: fix an aws s3 sync error when handling special file types during a synchronization operation

[RoseSecurity]

Why

Note

The following error is also present during systemd operations in ExecStartPre. The sync operation exited with a non-zero exit code (2), breaking the script due to set -e.

• Encountered the following when executing the following:

[root@hostname]# /usr/local/bin/teleport-all-pre-start
warning: Skipping file /var/lib/teleport/debug.sock. File is character special device, block special device, FIFO, or socket.

[root@hostname]# echo $?
2

What

• The script checks for the existence of debug.sock in the local /var/lib/teleport directory and removes it before starting the sync operation.
• The aws s3 sync command now uses the --exclude flag to correctly exclude debug.sock and other socket files from synchronization.
• Added error-catching mechanisms to gracefully handle aws s3 sync issues and log meaningful error messages.
• Ensures the script exits with an appropriate error code if critical files are missing after the sync.
• The script verifies the presence of required files (fullchain.pem and privkey.pem) after synchronization, ensuring a successful pre-start configuration.

Reference

• Sync Operations Issue

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}