Introducing vault sharing and the restrictions of pulling and cloning with vault permissions

[scottmmorris]

Description

This pull request aims to allow vaults to be shared and unshared with other node Ids. In other words the ability to overwrite (either set or unset) the vault permissions and have the agent check that the permissions for a node are valid for the clone or pull action that is being performed.

Issues Fixed

• Fixes Complete shareVault/unshareVault implementation #259

Tasks

1. Complete the share and unshare vault functions
   • Set the gestalt action for the node
   • Set the vault action for both pull and clone
   • Send a notification to the node (only for sharing)
2. Check the ACL for vault permissions in agentService
   • Send node Id and vault action metadata over GRPC
   • Access the relevant vault and node permissions in the ACL
   • Copmare the permissions and throw if not valid
3. Expand testing for vault sharing

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[CMCDragonkai]

Please add in the lintfixing related to vaults work: https://gitlab.com/MatrixAI/Engineering/Polykey/js-polykey/-/merge_requests/205/#note_712956648

[CMCDragonkai]

I have to recreate this PR because I deleted the base branch :(.

[CMCDragonkai]

Recreated here #262.