feat: signing and verification of memory transaction

[Gozala]

Changes here implements operation signing and verification. All operations are represented (roughly) as UCAN invocations and signed by a memory consumer key. Provider currently only verifies that:

1. Invoked operations is included in signed authorization.
2. That signature is from the invocation issuer.

Also please note that:

1. This implementation does not check whether issuer has authority over space (this will be built in the future on top).
2. This implementation does net yet integrate common-identity and simply uses web native ed25519 keys. Integration with common-identity will be add as followup.

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TypeError: Cannot read properties of undefined (reading 'pipeThrough') ?(/Users/jakedahn/common/labs/typescript/packag... View Issue

_{Did you find this useful? React with a 👍 or 👎}