Need strategy for updating settings after constructing agent class

[TimoGlastra]

In some flows it may be quite difficult to construct the agents with all config parameters already defined. This is easy from the point of AFJ, but in theory a lot of values could be delayed until later.

• Wallet config and credentials is not necessary until init is called
• genesis transactions / genesis path is not necessary until a connection with the ledger opnened
• ...

We have a flow where we construct the agent, but do not have the wallet credentials yet. After this we fetch the wallet key from secure storage to unlock the wallet and only then we call the agent.init() method.

---

One solution would be to allow to pass extra config to the init method, but this would mean more validation, less explicit typing.

Another method is allow to update config values and handling those update in the framework. (not sure how to do that yet, but should be possible). This is probably more work, but also more dynamic.

I would like some input from others as this will require modifications to how the framework is initialized