make commitment request optional

[himanshuchawla009]

Support added to make commitment request optional

Motivation and Context

This PR add supports to make commitment request optional. It does that by passing temp session keys and verifier to retrieve shares and import shares request.
Ideally this flow should be recommended only for mpc and multi factor setups. It should not be used in SFA flow.
This is done to improve login speed in cases where commitment request can be skipped.

Jira Link:
https://toruslabs.atlassian.net/browse/IRT-1536

Description

A new param named "checkCommitment" is added to retrieveShares and importShares function. By default its set to true to keep the change fully backward compatible.

Apps can now set this flag to false if they want to skip commitment req.

Previously session keys and verifier name was getting derived from node sigs in backend, this PR explicitly sends those fields in request if checkCommitment is set to false.

How has this been tested?

A new test case is added to run the flow without commitments.

Also i have tested the network calls manually to see if its actually skipping the commitment rpc calls.

Similar testing has been done on backend.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project. (run lint)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[arch1995]

lgtm