[FEAT] Add capability for a custom container entrypoint

[Coopyrightdmin]

Problem Statement

Users currently lack the option to set a custom entrypoint for the generated container. This restricts the container's behavior upon initialization to a default configuration.

Benefits

Implementing a custom entrypoint feature would:

• Provide users with the capability to determine the container's behavior at startup.
• Enhance flexibility, as containers can be tailored to specific tasks or applications from the onset.
• Improve the overall container usage experience by minimizing the need for manual configurations post-startup.

Additional context

Custom entrypoints are essential for scenarios where specific tasks or applications need to run as soon as the container is initialized. This feature would cater to advanced users who require this level of customization.

Priority/Severity

• [ ] High (This will bring a huge increase in performance/productivity/usability/legislative cover)
• [x] Medium (This will bring a good increase in performance/productivity/usability)
• [ ] Low (anything else e.g., trivial, minor improvements)

[Coopyrightdmin]

🎉 Feature Implemented!

Users can now specify a custom entrypoint for the generated container. This provides enhanced flexibility in determining the container's behavior upon startup. With this feature, containers can be tailored to specific tasks or applications right from the onset.