Avoid ESM failures when AWS V4 signing is unused

[mdlavin]

Alpha does not work well in a non-ESM because Axios, upstream, adopted ESM in their "unsafe" published source files. This sort of failure is common when adopting the latest Alpha version:

/Users/mattlavin/Projects/graphql-tools-cli/node_modules/@lifeomic/alpha/src/interceptors/aws-v4-signature.js:11
const buildURL_js_1 = __importDefault(require("axios/unsafe/helpers/buildURL.js"));
                                      ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/mattlavin/Projects/graphql-tools-cli/node_modules/axios/lib/helpers/buildURL.js from /Users/mattlavin/Projects/graphql-tools-cli/node_modules/@lifeomic/alpha/src/interceptors/aws-v4-signature.js not supported.

Luckily, the only place that "unsafe" (aka ESM) modules are imported is in the AWS V4 signing support and that is very infrequently used. By making this change, it reduces the failure to only modules that use AWS V4 (nearly nobody and they must already have to deal with it)

This change doesn't avoid the problem completely, but it significantly reduces the impact.

[shawnzhu]

great fix.

Have you trying to upgrade Alpha for repos already?

[mdlavin]

How did you discover this problem?

I have run into some variation of the failure in the description every time I try to adopt the latest Alpha in a project. I was finally sick of the problem and wanted a better fix. The error message was pretty helpful at pointing out the problem. I went through a couple different solutions before I ended on this as "best for now"

[mdlavin]

Have you trying to upgrade Alpha for repos already?

As soon as this as this builds, I'm going to put up a fix to an internal project and I'll add you to the PR