Note: @shamilovtim's Additions
Users want to be able to provide custom optionality to the UserAgent used by Web5.connect
We should be able to do this without bloating the params and argument drilling all of the params through multiple methods
Therefore we could allow users to pass a custom Web5 User Agent in order to solve this problem
This should eliminate the agentVault param

For example, to add dataPath as a parameter for Web5.connect() method. The dataPath should be forwarded to this request within the connect method:

const userAgent = await Web5UserAgent.create({ agentVault });

If this create method is provided with dataPath, it could be possible to have separate databases locally on the same app.