fix(dev): Hide spam warnings from babel-plugin-module-resolver

[zetlen]

Description

Fixes #880. We use an interceptor API for the plugin's resolvePath function, which simulates the environment variable while the plugin runs. This works and suppresses the warning, so we removed the explanator console.warn() call as well.

Related Issue

Closes #880.

Motivation and Context

Devex is a primary quality measure of this project, and useless worrisome console output is one of the worst things for devex.

How Has This Been Tested?

Tested in all environments and Node versions.

Screenshots (if appropriate):

Compare to screeshot in #880:

Proposed Labels for Change Type/Package

BUG
Improved devex

Affects venia-concept, even though changes are in root babel.config.js

Checklist:

• I have read the CONTRIBUTING document.
• I have linked an issue to this PR.
• I have indicated the change type and relevant package(s).
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All CI checks are green (linting, build/deploy, etc).
• At least one core contributor has approved this PR.

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

[sirugh]

tleunen/babel-plugin-module-resolver/pull/351 is merged. Can you update this PR accordingly?

[jimbo]

Devex is a primary quality measure of this project, and useless worrisome console output is one of the worst things for devex.

Totally agree. 👍

Please review the plugin PR and let's get this updated and merged!

[zetlen]

Oh nice! Updating now.

[coveralls]

Coverage remained the same at 62.131% when pulling 865df0d on zetlen/hide-babel-module-warnings into e4568a8 on release/2.0.

[zetlen]

@sirugh How's this?

[sharkySharks]

These changes look good to me. I built it locally, did not see the warnings, and the app served as expected.