Support parameter override

**Describe the enhancement**
The config setup forces users to parse toml files or manually modify them to change things like rpc credentials.
Some users might not need modification of these, but in some setups these change continuously, forcing the user to use other tools to modify these files, adding additional dependencies to the setup.

**Use case**
I'm using bdk-cli mainly for testing. Maybe there is a good reason to not give too much freedom to the user to change parameters of their configuration, but I think at least RPC parameters are certainly prone to change, even more if the node is using cookie authentication.

**Additional context**
I updated the bdk-cli in the `bdk-sp` nix environment, and it broke most of the commands I was using to wrap bdk-cli. Some of the changes are useful, like writing keys into file, but some others are not, like rpc credentials. I'm starting and stopping this node very frequently and the rpc cookie changes each time. I had to add a tool like `dasel` to modify the parameters I need in the file.

Beginne mit der Konfigurationseinrichtung von bdk-cli und der in der Issue beschriebenen TOML/RPC-Parameterverarbeitung. Konzentriere dich darauf, wie RPC-Zugangsdaten und die Cookie-Authentifizierung geladen werden. Verfolge die relevanten CLI-Einstiegspunkte und überprüfe, dass wiederholte Node-Neustarts geänderte Zugangsdaten ohne manuelle Dateibearbeitung verwenden können, während das bestehende Konfigurationsverhalten erhalten bleibt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.