fix(azure-key-vault-driver): fix character encoding

[itpropro]

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)

📚 Description

• Updated key encoding/decoding to avoid decoding errors
• Updated docs with additional usage hints

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
unstorage	Edit on Studio ↗︎	View Live Preview	916e551

[pi0]

Would it makes sense / be possible that we use url encoding? (= ~> %3D)

[itpropro]

Unfortunately not, as Key Vault only supports dashes besides alphanumeric characters. This replacement is only necessary because of the potential characters that could result in a base64 encoding. B64 was the only encoding I found that is available without adding an additional dependency and without requiring a custom implementation of an encoding scheme. As dashes are the only allowed characters and there were too many edge cases with replacing the special characters of b64 with alphanumeric characters or only one dash, this was the least overhead solution.
I can add an additional test of course to validate the encoding.

[codecov]

Codecov Report

Merging #308 (d6364ca) into main (e41a1df) will increase coverage by 0.00%.
Report is 6 commits behind head on main.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #308   +/-   ##
=======================================
  Coverage   77.96%   77.96%           
=======================================
  Files          29       29           
  Lines        3417     3418    +1     
  Branches      521      521           
=======================================
+ Hits         2664     2665    +1     
  Misses        752      752           
  Partials        1        1           

Files	Coverage Δ
src/drivers/azure-key-vault.ts	36.84% <100.00%> (ø)

... and 1 file with indirect coverage changes

[pi0]

Thanks!