Additional test cases needed to be support by the Mobile Backchannel

[swcurran]

The mobile backchannel allows the execution the "Bob" role in a run of Aries interop tests to be carried out by a mobile wallet operated by a person. The activities of the other roles (Acme, Faber and Mallory) are performed by one of the fully automated backchannels -- initially (until #560 is implemented) just Aries Cloud Agent Python.

While the existing Mobile Backchannel supports some tests (notably those using AIP 1.0), we'd like to include more tests that can be run by mobile agents -- especially those focused on AIP 2.0 for establishing connections and credential exchange. To do that, we need to do the following:

1. Review the "not yet supported" tests and identify those where the activities of Bob are likely to be supported by a Mobile Wallet.
2. Update the Mobile Backchannel to support the steps in those tests.
3. Document the additional tests that can be run and add appropriate tags to those tests to allow them to be selected and run.

In doing 1, keep an eye out for tests where other than "Bob" is being used in a role that is not "Bob", but is supported by a mobile wallet. In such cases, we may (or may not) when to adjust the test to have "Bob" play the wallet role. For example, the test @T005-RFC0023 has Bob with a resolvable DID, which a wallet would generally not have. It would be better to that test with Bob's and Acme's roles swapped, or perhaps with Acme and Faber, if the intention is that wallets would not be involved.

• Issuer Cred V2 Proof v2, OOB, handling in the Mobile Backchannel.

• Choosing the ICV2 and PV2, OOB tests to tag as MobileTests

• There are ICv2 tests that start with an offer not a proposal that need to get out of the wip state. It may be uncommented and work without any or much work.