create-container: Update Containers on an interval

[runleveldev]

Issue: Automate container template updates and pre-apply fungible configuration

Description:
Container templates are currently static and require manual updates or reconfiguration. This can lead to outdated configurations and unnecessary manual intervention.

Recommendation:

• Implement automatic synchronization of container templates from their upstream sources on a defined interval.
• Pre-apply fungible configuration values (e.g., LDAP settings, default environment variables) that do not depend on runtime-specific details such as hostname or IP address.

Benefits:

• Ensures templates remain current with upstream improvements and security patches
• Reduces manual maintenance workload
• Enables faster, more consistent provisioning
• Improves reliability of automated deployments

[runleveldev]

See ChatGPT link for the strategy I want to employ which will cover both this issue and #35
https://chatgpt.com/share/68f95622-d220-8004-9901-d64c5536db80

[runleveldev]

This will best be implemented as a 2 part PR. First implement the Hashicorp Packer build process and automation, then once the builds are tested and working in main, update the container creation process to build a new container from that template rather than cloning the given LXC ID.

[runleveldev]

In addition to running updates on the container (Proxmox would do that for us) we should also be applying the pown.sh modifications, Wazuh, and any other pre-install modifications. Since packer handles the build in a chroot, Wazuh shouldn't try to register until the first boot of a container. Likewise those scripts should be removed from the container creation flow.