Implement handler to wrap fs.writeFile functionality

[aryanjassal]

Description

Currently, the VaultsSecretsEdit handler uses vaultOps.updateSecret() to update a secret's contents if it exists. Otherwise, it throws an error. This behaviour convolutes the implementation for secrets edit and secrets write as a lot of needless checks are run at the client side to work around a small oversight.

As such, this PR will aim on laying the groundwork for secrets write by creating a handler which will write secret contents to a secret. If the secret doesn't exist, it will automatically get created.

Issues Fixed

• Relates to Polykey-CLI#242
• REF ENG-355

Tasks

• 1. Remove VaultsSecretsEdit
• 2. Add VaultsSecretsWriteFile
• 3. Create vaultOps.writeSecret as a wrapper around fs.writeFile
• 4. Make tests for VaultsSecretsWriteFile
• 5. Make tests for vaultOps.writeSecret

Final checklist

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

[linear]

ENG-355 Implement `secrets write` command

[aryanjassal]

Currently, we are using a UnaryHandler to update secrets. For consistency, this behaviour needs to be replicated over to the VaultsSecretsWriteFile handler too.

However, UnaryHandler is inherently not a good choice for streaming file contents. A better choice would be a RawStream, but it needs more work and discussions to set up. As such, it will be done in later iterations. For now, the new handler will keep using UnaryHandler but use the new vaultOps function.

[tegefaulkes]

I skimmed through it and nothing stands out. Looks good.

[aryanjassal]

Everything for this PR has been done and approval has also been granted. Merging.