Feat/optional arch specific binaries

[YOU54F]

The following PR will

support libpact_ffi & pact-js-core node bindings to be published in seperate npm packages.

these are segmented by ${os}-{arch}-{libc}

users should not need to require these automatically, npm should determine the required
optional dependency to download at install time.

supported_platforms

"@pact-foundation/pact-core-darwin-arm64": "16.0.0",
"@pact-foundation/pact-core-darwin-x64": "16.0.0",
"@pact-foundation/pact-core-linux-arm64-glibc": "16.0.0",
"@pact-foundation/pact-core-linux-arm64-musl": "16.0.0",
"@pact-foundation/pact-core-linux-x64-glibc": "16.0.0",
"@pact-foundation/pact-core-linux-x64-musl": "16.0.0",
"@pact-foundation/pact-core-windows-x64": "16.0.0"

CI Improvements

Significant build time reductions, by reducing the times when prebuilds are created.

• libpact_ffi node bindings as prebuilds will only be created on master
• test suite will download the latest release prebuilds via gh cli, if not on a master branch

This could be further improved to

• build node bindings & prebuilds, on pull requests, where
  • the libpact_ffi version has changed
  • the code in native or the bindings.gyp changes
• allow top level job conditional skipping.
  • it appears you cannot skip an entire job based on a condition, which is a pre-requisite for another job, so you have to nested the condition at each step level.

Testing

Consumed in pact-js, via scoped publish, shown tested in following forked PR

• You54f prebuilds YOU54F/pact-js#3

Has been tested with yarn and npm, but ideally wants testing with pnpm as well prior to release