Upgrade to node-fetch v3

We use `node-fetch` as the underlying fetch library many places in our code:

node-fetch-retry: https://github.com/adobe/node-fetch-retry/blob/master/package.json#L13
node-openwhisk-newrelic: https://github.com/adobe/node-openwhisk-newrelic/blob/master/package.json#L14

In some cases, we use a deprecated `node-fetch-npm` library:

node-httptransfer: https://github.com/adobe/node-httptransfer/blob/master/package.json#L26

We should be using the newest stable version of node-fetch (v3), which has breaking changes everywhere in our code to lessen the tech debt.

https://github.com/node-fetch/node-fetch/releases/tag/v3.0.0

ideally move to at least 3.1.1: https://github.com/node-fetch/node-fetch/releases/tag/v3.1.1 (or the most recent v3 version)

Note: v3 is now an ESM package.

Start with package.json and the node-fetch-retry, node-openwhisk-newrelic, and node-httptransfer dependency references named in the issue. Read the node-fetch v3.0.0 and v3.1.1 release notes, especially the ESM migration requirements, then inspect affected usage across the referenced packages. Done means the deprecated dependency is removed and the packages use a current v3 release without breaking their existing behavior.

Written by the indexing model from the issue text.