Increase ties and testing between nodenv/node-build and asdf-nodejs

[jasonkarns]

I'm the primary maintainer of nodenv (and node-build). Recognizing that asdf is (I believe) the most notable consumer of node-build outside of the nodenv org, I'd like to discuss ways to improve the stability of the projects.

I'm looking to redevote some more time to nodenv/* in the coming months and the largest portion of that attention will be to backport the latest changes from rbenv/ruby-build downstream to node-build. This will mean a bunch of changes in node-build so I'd like to discuss ways that can prevent node-build from causing issues with asdf.

Some non-mutually-exclusive ideas:

• have some asdf members join the nodenv team
• get some asdf team members to review PRs on node-build
• build out some integration tests within node-build's suite that exercise node-build through asdf
• construct some pre-release pipeline to vet major changes with asdf prior to release
• others?

[jasonkarns]

An example (tiny) PR that I would love to have some ASDF eyes on: nodenv/node-build#885