Updated pkgs.nix to a5774e76bb8c3145eac524be62375c937143b80c
Updated node2nix to 1.11.0 and loading directly from GitHub
Updated pkg to 5.6.0 and using pkg-fetch 3.3 base binaries
Updated to TypeScript 4.5+
Updated @types/node to 16.11.7
Updated node-gyp-build to 4.4.0
Updated typedoc to 0.22.15, the .nojekyll generation is automatic
Changed to target ES2021 as node 16 supports it
Bin executable duct-tape in default.nix because node2nix no longer generates bin executables
Updated pkg builds hashes to v16.14.2 and specified target node range

Updated js-async-init from 1.6.0 to 1.7.1
Updated js-async-locks from 2.0.0 to 2.2.0
Updated js-db from 3.2.0 to 3.2.3
Updating js-workers from 1.2.5 to 1.3.1

The `data` POJO that was originally supplied in the constructor as the second parameter is now part of the `options` parameter and most places in the code have been updated to match this.

When any error is thrown as the result of another error occurring, the original error is now contained within the `cause` property of the new error.

#304

#304

#304

#304

…or chaining

Our gRPC `toError` and `fromError` utils are now able to serialise and deserialise Polykey and non-Polykey errors (as well as non-errors), including the entire error chain if this exists. Also includes the ability to filter out sensitive data, for example when the error is being sent to another agent.

Errors sent over the network in this way are now additionally wrapped on the receiving side in an `ErrorPolykeyRemote` to make the source of the error more clear.

#304

All of the agent and client service handlers are now passed a shared logger that is used to log errors to stderr.

#304

Note that the `transaction` and `_transaction` methods still need te removed.

I opted not to use transactions for the most part. Adding things to the queue has to be handled with locking anyway so I opted to rely on that istead. This still bears testing though.

Updated the locking and some changes to the transactions

Fix into the vaults domain DB changes. Some tests are still failing but they relate to the `PolykeyAgent` failing to start.

This was throwing an error because the expected object structure changed. The typing is brittle here since we're going around typescript's back to get a private property.

Sequence numbers and claim ids needed locking due to serialisation concerns

Notifications have strict ordering in the DB, therefore locking is required.

There are still some tests failing due to cloning and pulling. Seems like a problem with the HTTP API for cloning.

There was a bug with the `fromJSON` method where it couldn't deserialise an error with an undefined cause (because this is removed by the replacer)

…ors properly

Making use of the updated API to use the error provided to the resourceRelease.