monero-cli: non-interactive wallet generation
Hi,

I've been testing around with monero-cli a bit and I do really like Monero as Project and concept, tho one feature I'm missing is the ability to *non-interactively* generate wallets.

When running ```./monero-wallet-cli --create-address-file --password [REDACTED] --mnemonic-language English --generate-new-wallet ./new.wallet ``` I get not just some output in the form ```new.wallet```, ```new.wallet.keys``` and ```new.wallet.address.txt``` but also have to deal with the whole interactivity, which I don't want to.

````
This is the command line monero wallet. It needs to connect to a monero
daemon to work correctly.
WARNING: Do not reuse your Monero keys on another fork, UNLESS this fork has key reuse mitigations built in. Doing so will harm your privacy.

Monero 'Fluorine Fermi' (v0.18.3.1-release)
Logging to ./monero-wallet-cli.log
Generated new wallet: 
[REDACTED]
View key: [REDACTED]
**********************************************************************
Your wallet has been generated!
To start synchronizing with the daemon, use the "refresh" command.
Use the "help" command to see a simplified list of available commands.
Use "help all" command to see the list of all available commands.
Use "help <command>" to see a command's documentation.
Always use the "exit" command when closing monero-wallet-cli to save 
your current session's state. Otherwise, you might need to synchronize 
your wallet again (your wallet keys are NOT at risk in any case).


NOTE: the following 25 words can be used to recover access to your wallet. Write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.

[REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED]
[REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED]
[REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED] [REDACTED]
**********************************************************************
The daemon is not set up to background mine.
With background mining enabled, the daemon will mine when idle and not on battery.
Enabling this supports the network you are using, and makes you eligible for receiving new monero
Do you want to do it now? (Y/Yes/N/No): : N
Background mining not enabled. Set setup-background-mining to 1 to change.
If you are new to Monero, type "welcome" for a brief overview.
Error: wallet failed to connect to daemon: http://localhost:18081. Daemon either is not started or wrong port was passed. Please make sure daemon is running or change the daemon address using the 'set_daemon' command.
Background refresh thread started
[wallet [REDACTED] (no daemon)]: exit
[REDACTED]@[REDACTED]:$ 
````

Not only is it ```interactive```but it doesn't really scale well and whilst one could [workaround some of these by using ```pipe```](https://monero.stackexchange.com/questions/10385/creating-a-wallet-in-non-interactive-mode-using-monero-wallet-cli/10395#10395), this doesn't scale well nor does it save the *mnemonic recovery phrase* at all.

Personally, a lot of my tools like [```mkp224o```](https://github.com/cathugger/mkp224o) and [```enc```](https://github.com/life4/enc) allow [scripting entire workflows](https://github.com/life4/enc?tab=readme-ov-file#armordearmor-the-message) making it easy to [alias recurring actions](https://github.com/kkarhan/misc-scripts/blob/master/bash/.bash_aliases#L55).

---

Proposed solution:

Add a ```---batched``` and/or ```---non-interactive``` flag to ```monero-wallet-cli```, parsing i.e. a ```batch.conf``` or ```non-interactive.conf``` file where one could define the parameters like language for the *mnemonic recovery seed* anlong side other parameters, allowing to automate wallet generation and potentially even transfers to said wallets.

For example ```monero-wallet-cli --non-interactive``` would generate a new folder named ```wallet```, automatically choose a secure password [i.e. running ```< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c${1:-128};echo;``` for a 128 digit, [secure password](https://www.howtogeek.com/howto/30184/10-ways-to-generate-a-random-password-from-the-command-line/)]. and write all the info into it, resulting in the following structure:

````
├── wallet 	
    ├── wallet.address.txt
    ├── wallet.mnemonic.txt
    ├── wallet.view.key.txt
    ├── wallet.wallet
    └── wallet.keys
````

Basically acting like a CLI version of [Monero Wallet](https://github.com/xmraddress/xmraddress.org) [Generators](https://monero-wallet-generator.com/) like the [one orphaned  who's code I keep online](https://github.com/kkarhan/paperwallet)... 

---

Use-Cases:

This would enable the design of *Monero Voucher Generators* that similar to  [Prepaid Cards](https://en.wikipedia.org/wiki/Stored-value_card) like [Paysafecard](https://en.wikipedia.org/wiki/Paysafecard#Functionality) could generate wallets on the fly and even load them with balance if desireable.

These could then print-out the ```wallet.address.txt```, ```wallet.mnemonic.txt``` and ```wallet.view.key.txt``` on thermal paper [or even generate [QR Codes](https://en.wikipedia.org/wiki/QR_code) for these as well] making it trivial to use these on the go - both offline and online.



Furthermore it makes integration of Monero simpler for 3rd party applications like online payment.

---

Looking into existing solutions:

As of writing, I've [not](https://monero.stackexchange.com/questions/7464/how-to-communicate-programmatically-with-the-monero-cli-wallet-using-php/7465#7465) [really](https://monero.stackexchange.com/questions/11043/how-to-generate-a-monero-wallet-programatically/11046#11046) found a good solution to this problem.