feat(client) [NET-1269]: Add support for publishing on behalf of an ERC-1271 contract

[harbu]

Summary

Add new signature type ERC_1271 that can be used to publish messages on behalf of a smart contract implementing ERC-1271.

Usage

const client = new StreamrClient({
  auth: {
    privateKey: '<REDACTED>'
  }
})

/* 
  Behind the scenes a call to contract method `isValidSignature` is performed to verify that 
  the client wallet address is a valid signer for the given contract.
*/
await client.publish('foobar.eth/hello/world', {
   key: 'value 
}, {
  erc1271contract: '0xc0ffee254729296a45a3885639AC7E10F9d54979' 
})

Misc changes

• Fix fake timers behavior in browser test runner
• Fix describe.each in browser test runner
• Add signature type of MessageMetadata interface
• Add groupKeyId to MessageMetadata interface
• Revert commit where recoverSignature was removed from @streamr/utils exports. Add back unit tests too.
• Move MapWithTtl to @streamr/utils. Add unit tests.

Limitations and future improvements

• A symmetric feature would be being able to subscribe on behalf of an ERC-1271 contract. This will be implemented in an upcoming PR.
• We could abstract different signature methods as sort of base interface and then implementations for each.
• Instead of injecting instantiateContracts we could actually inject getStreamRegistryChainProviders to even more narrowly abstract the changing factor.

Checklist before requesting a review

• Is this a breaking change? If it is, be clear in summary.
• Read through code myself one more time.
• Make sure any and all TODO comments left behind are meant to be left in.
• Has reasonable passing test coverage?
• Updated changelog if applicable.
• Updated documentation if applicable.

[linear]

NET-1269 Add signature type to support EIP-1271 (needed by DIMO)

[harbu]

Review with @teogeb , will address these