Resolve Pin Issues

[maneeSHA-256]

Issue

This PR is addressing the following issues :

1. No pins on newly generated local test tokens : there was no pin while first transferring a newly generated token, leading to unpin error logs on sender node
2. Adding token-state-hash inplace of token-hash to TokenProviderTable of receiver : Receiver was adding token state hash instead of token hash in Provider table. So, when the receiver transfers, it never finds the tokens in Provider table and hence never removes the token details from the table.
3. Multi-pin check failure : Quorum was fetching the providers list of the token-hash. But while inquiring about the pin role, quorum was passing token-id instead of token-hash. So, when the providers checks its' Provider table it does not get any info, returning false to quorum. Quorum passes multi-pin check due to absence of correct info.

Solution

1. Token owner is pinning the test tokens while generating them
2. Receiver is adding token hash to TokenProviderTable. Hence, it is successfully getting removed whenever the token is transferred further.
3. During multi-pin check, Quorum is inquiring about the token-hash pin role instead of token-id pin role.