Add did:indy transaction version 2 support

[jamshale]

This adds the ability to create a did:indy with transaction version 2 algorithm. https://hyperledger.github.io/indy-did-method/#nym-transaction-version.

• It's created in a new /did/indy/create endpoint. If the controller tries to create it in the /wallet/did/create endpoint it will get a indy method not supported (same as before) and tell them to use the new endpoint.
• Adds seed support with allow-insecure-seed configuration
• When starting up an agent wither a did:indy or did:sov seed can be used.
• Does a refactor on wallet startup function to reduce complexity.

[jamshale]

The security alerts are nothing. http used in the scenario tests. Not sure how to ignore it yet.

[dbluhm]

I like what you're doing in this PR -- really appreciate the wallet startup cleanup as well. Question: how do we get the DID onto the ledger? Are we saying this is handled out of band?

[jamshale]

It's the same way as a did:sov. You use the /did/indy/create and then post it to /wallet/did/public. There's no way to start up a fresh agent with a seed and a did:indy currently. Doing that with a seed still creates a did:sov.

Edit: oh, to get it on the ledger you just post the did:indy:12345 and the verkey. So, yes I think that would be out of band.

[sonarcloud]

Quality Gate failed

Failed conditions
2 Security Hotspots

See analysis details on SonarCloud

[dbluhm]

Couple of quick comments but otherwise looks good!

[dbluhm]

You're doing as the Romans do here but I think this logic ought to be captured directly in DID registration/creation endpoints. This "centralized" logic made sense when there was a single endpoint for creating DIDs but, "decentralizing" the logic, as we've talked about doing and as you've done here for did:indy, I don't think it's necessary for this to all be in one place.

[dbluhm]

Setting DID Endpoint in this way will get picked up by the legacy resolution support in Indy VDR but doesn't get picked up by the universal resolver, just as an aside. Ideally, we set this by updating the nym with diddocContent rather than with an attrib. We can address that in the future, though, of course.