payjoin-cli should have allow saving configs

[nothingmuch]

As a following up on #874, we should create a default config file.

The simplest idea i have is: payjoin-cli can have an additional boolean --set-config flag, that takes the config relevant clap arguments' values and saves them into the cargo.toml file (either the one in the current directory or the one in ~/.config/payjoin-cli, which should be the default if neither exists).

For ease of use/discoverability, a payjoin-cli configure command could take the same clap args as the other commands, and defaults config saving to true, but is otherwise a noop.

If no file exists, the example config file should be used but with the dummy values commented out (e.g. don't actually set rpcpassword = "password") before saving the given values.

[zealsham]

i'll follow this up , once #874 goes in

[arminsabouri]

A bit late to the party here. Will this issue help with developer experience? Looking for some clarity on what problem we are actually solving.

[zealsham]

@nothingmuch i'm thinking this goes against #1482 , and thinking of closing the initial PR i opened (#947) to address this as well as the issue too. saving or not saving config isn't entirely a payjoin thing , what do you think ?

[nothingmuch]

agreed, this seemed like a good idea to me at the time but in hindsight not so much