Feature/181 support updated auth storage node

[tahpot]

Closes security issue: https://github.com/verida/security-issues/issues/1

Implements changes required to support talking to updated storage node: verida/storage-node#14

[tahpot]

Latest commit has all unit tests passing in client-ts (except one that is broken in main):

yarn run tests
yarn run v1.22.15
$ ts-mocha './test/**/*.ts'

Network initialization tests
Initialize network connection
✓ can create a network instance

Basic vault tests
Test connecting
✓ can open vault context

Profile tests
Public profiles
✓ can initialise own profile (2135ms)
✓ can not set invalid profile values (181ms)
✓ can access an external profile (788ms)

Schema tests
Basic schema tests
✓ can open a known schema specification (227ms)
✓ can fetch a known schema JSON (218ms)
✓ can validate correctly
✓ can get appearance
✓ can generate versionless scheams

Storage context tests
Initialize user storage contexts
✓ can open a user storage context when authenticated (1570ms)
✓ can open a database with owner/owner permissions (307ms)

Storage initialization tests
Initialize user storage contexts
✓ can not force create a user storage context if not authenticated
✓ can authenticate a user
✓ cant open a user storage context that doesn't exist, even if authenticated (423ms)
✓ can force open a user storage context that doesn't exist when authenticated (856ms)

Verida database connectivity tests
Manage databases for the authenticated user
✓ can listen for sync events (10574ms)
✓ can stop triggering events if listener is cancelled (10046ms)
✓ can fetch sync info

Verida database tests relating to contexts
Database read / write works across contexts
✓ can open a database with public write permissions (961ms)
✓ can read from an external database from a different context (480ms)
✓ can write to an external database from a different context (114ms)

Verida database tests
Manage databases for the authenticated user
✓ can open a database with owner/owner permissions (659ms)

Verida database registry tests
Manage databases for the authenticated user
✓ can open owner/owner database with valid registry entry (621ms)
✓ can open owner/owner database and not save a registry entry (319ms)
✓ can update permissions of existing registry entry (229ms)
✓ can open public database with valid registry entry (267ms)

Verida database tests
Manage databases for the authenticated user
✓ can open a database with owner/owner permissions (900ms)
✓ can open an existing database with user permissions (407ms)
✓ can create a new database defining initial users (1017ms)
✓ can open a database with public read permissions (124ms)
✓ can open a database with public write permissions (120ms)
Access public databases
✓ can read from an external database with public read (368ms)
✓ can't write to an external database with public read, but owner write
✓ can write to an external database with public read and public write (74ms)
✓ data saved to external database has valid signature (256ms)
✓ can't open an external database with owner read and not the owner
✓ can't write to an external database with write=users and read=public, where user has no access
Access user databases
✓ can read and write from an external database with read=users where current user CAN read (206ms)
✓ can't read from an external database with read=user where current user CANT read (245ms)
✓ can't write an external database with write=users and user no access (283ms)
✓ can't open an external users database without an encryption key
✓ can't open an external users database with the wrong encryption key (178ms)
✓ can't write an external database where a did has read access, but not write access (226ms)

Verida datastore tests
Manage datastores for the authenticated user
✓ can open a datastore with owner/owner permissions (799ms)
✓ can open a datastore with user permissions, as the owner (160ms)
✓ can open a datastore with user permissions, as an external user (872ms)
✓ data signatures correctly drop version information from signatures (56ms)

Verida messaging tests
Sending messages
✓ can send a message between users of the same application (2449ms)
✓ can receive a message from a user of the same application (505ms)
✓ can trigger an event on a new message (334ms)
✓ can send a message between two different users of different applications (918ms)
✓ can receive a message from a user of a different application (602ms)

Verida notification tests
Sending messages
✓ can specify a notification server when creating a new account context (906ms)
✓ can force add a notification server to an existing account context (1749ms)
1) can ping a notification server when sending a message

55 passing (53s)
1 failing

[tahpot]

This is fully tested and working well.

Depends on the following PRs before completion:

• Storage Node (Fix/13 improve auth security storage-node#14)
• Vault Mobile (https://github.com/verida/vault-mobile/pull/706)