completed: draft all gpg key function names

I decided to prioritize developer experience and provide simplified, high-level functional abstractions instead of maintaining 1:1 parity with the underlying gpgme library functions. See example in T8021

I may have misinterpreted what The GnuPG UI Server Protocol is. Instead, I will provide high-level functions to all of gpgme's underlying features

Published to NPM as gpgmejs, which provides disambiguation from gpgme, gpgmepp, gpgmepy, etc.

completed working test and repo:
https://github.com/anthumchris/gpgmejs/

Thanks. Could you please clarify if the even-numbered minor version (2.2.x, 2.4.x, 2.6.x, etc) rule is still required? I'd like to provide clarity to the Homebrew team avoid any potential ambiguity

Completed working base repository with developer workflows for watching files and rebuilding/retesting:
https://github.com/anthumchris/node-addon

• --experimental-addon-modules stability for javascript ESM import syntax

Thanks, I'll start here and see how it was done with JS for the browser: https://dev.gnupg.org/source/gpgme/browse/master/lang/js/