Added a batch option

[lap1nou]

Hello,

Description

This PR adds a -b / --batch option to answer all Confirm() call by the default value, this can be useful in case of unattending installation, for example, if Exegol is deployed at scale using Vagrant / SSCM / ...

Related issues

N / A

Point of attention

I only tested a classic exegol install osint -b, I hope this won't break anything.

[ShutdownRepo]

Fixed the target branch, can you resolve the conflicts?
I'll let @Dramelac then review the PR, as there's somethings very similar in his todolist somewhere if I remember correctly

[Dramelac]

Hello @lap1nou,

Thank you for your PR, this feature is on our roadmap as @ShutdownRepo mentioned but hasn't been completed yet because of its complexity.
Exegol is very flexible to allow a seamless experience for the user and the Confirm function isn't the only one concern by this feature to fully enable a non-interactive mode.

I will keep your PR on hold for now because there is a lot missing. But, if you have some time to go further i can go into more details. Otherwise i will handle this subject later.

[lap1nou]

Hey @Dramelac, @ShutdownRepo, thank you for your answers.

If you have other examples of things to change I can try to dig into the subject.

Regards.

[Dramelac]

To give you more insight, Exegol has been thought for its UX priority, when an important information is missing, an interaction with the user will be requested. I had started a draft of ParametersManager().interactive_mode to disable the interactive behavior and identify the parameters to be considered critical to block the execution of the program immediately.
I didn't have too much time to think about the system until the end but currently we don't really use the "required": False of the groupArgs of each action, it can become a relevant tool in this feature.

Otherwise here are some cases where a user interaction will be requested:

• choose a container
• choose an image
• all kind of Y/N confirmations (delete, multi-select etc)
• configuration changes according to some options (however, the default choice proposed to the user should not necessarily be the one to apply in non-interactive mode, for example when a VPN is configured, exegol wrapper will propose to disable the network mode host, in non-interactive mode it is not necessary to follow the default choice which is to change otherwise it would block this option)
• the choice of image build profile
• the choice of git branch for checkout
• and probably other type i'm forgetting here...

In each case we have to choose if we want to disable or if we want to take an arbitrary choice. In cases where a CLI option is possible, why not make a critical parameter if its use is justified for example the choice of build profile is mandatory but the change of branch can be ignored if there are no parameters

Here are some issues / thoughts I had on the subject, if you want to take the subject and start to do things let me know so I do not launch equivalent work alongside.

[Dramelac]

In this state it's not enough to be merge into the wrapper