Add victory-vendor package for d3 dependencies

[becca-bailey]

This PR addresses the ESM-only package issues from d3 packages discussed in #2124

We take a two-path approach in that ESM uses the real ESM-only packages and CJS uses our vendored (transpiled) package versions.

Tasks

Stuff we still need to do:

• Validate victory-native still works as expected.
• Confirm storybook works as expected.
• Docs: the build fails for victory-vendor
• Docs: A build failure doesn't fail CI
• Review and remove all TODOs.
• Additional CHANGELOG.md notes.
• Fix it.skip()-ed Karma tests.
• Our yarn nps lint.docs command does not presently run in CI. It has a unique constraint in that both the root and docs dependencies need to be installed for it to succeed. We can either fix / enable here or maybe ticket for later.

Work

New stuff:

• Add new victory-vendor package.
• Added a super-simple Node.js test to flush out future ESM issues faster. See Tests: Add Node.js / SSR tests. #1965

Chores:

• Upgrade various babel deps that needed to be modernized.
• Refactor and simplify babel and webpack configs.
• Added more helper development commands in CONTRIBUTING.md

Fixes / infra:

• Shore up our import strategy for Jest and Karma. Now we only use built lib code in tests (ESM in Karma, CJS in Jest). Unfortunately this touches a lot of files and we end up with a big PR.

Release notes

We'll be publishing a new package victory-vendor, so I'm not sure if there are extra kinks in the release script there.

Also, for this release, since we've got a new vendor dependency scheme in the package, there are potentially some unforeseen issues that we won't be able to fully suss out until we fully release.

[becca-bailey]

These changes look good to me! @ryan-roemer You can go ahead and merge whenever you are ready, and then we can get this package released.

[becca-bailey]

I'm not sure why there is a diff in Chromatic, but there are no visible changes. I'm assuming there is just some microscopic difference because of a slight change to the d3 scale that it is picking up on. I'll approve those changes.

[becca-bailey]

@ryan-roemer I'm reviewing changes in chromatic, and there do appear to be a couple places where commenting out those scales changed things. I think we needed one of those log scales? There are also a few mysterious markup changes in the svg container, so I can investigate those a little more.

[ryan-roemer]

@becca-bailey Sounds good and good to know those Chromatic tests can flag this for us!!!

I'm holding off pending your investigation.

[becca-bailey]

From what I can tell, the axis label changes introduced in this PR have to do with changes introduced to the scale.tickFormat function in the d3-scale package. Here is more info about d3's default formatting. https://github.com/d3/d3-format/blob/main/README.md#locale_formatPrefix

This showed up as a diff in Chromatic, and users might notice some minor changes to the way log scale values are formatted by default. We will include some guidance in the release notes for the next version about Victory's tickFormat prop and how users can override the d3 default with their own formatting functions.