Add a reproduction for module rules not applying to a resource added by a plugin

[ezzatron]

This PR is trying to demonstrate a reproduction of the issue described in #17747, so that we can try to find a fix that doesn't also add a regression for #16466.

I'm submitting a draft PR, because it makes no sense to merge until a fix is found.

What kind of change does this PR introduce?

This PR adds a new statsCases test case, that when run, currently produces an error like:

$ yarn jest StatsTestCases -t issue-17747
yarn run v1.22.19
$ node --expose-gc --max-old-space-size=4096 --experimental-vm-modules --trace-deprecation node_modules/jest-cli/bin/jest --logHeapUsage StatsTestCases -t issue-17747
 FAIL  test/StatsTestCases.basictest.js (50 MB heap size)
  warmup
    ○ skipped should warmup webpack
  StatsTestCases
    ✕ should print correct stats for issue-17747 (210 ms)

...(snip)...

  ● StatsTestCases › should print correct stats for issue-17747

    Child compilation failed:
    Module parse failed: Unexpected token (1:8)
    File was processed with these loaders:
     * ./loader.js
    You may need an additional loader to handle the result of these loaders.
    > {"asset":"3ee037f347c64cc372ad.txt"}:
    SyntaxError: Unexpected token (1:8)

      39 |           .join("\n");
      40 |
    > 41 |         throw new Error(`Child compilation failed:\n${errorDetails}`);
         |               ^
      42 |       }
      43 |     }
      44 |   };

      at handleMake (test/statsCases/issue-17747/plugin.js:41:15)

...(snip)...

You can also demonstrate that this test passes if you comment out the following lines from NormalModuleFactory.js:

webpack/lib/NormalModuleFactory.js

Lines 528 to 530 in 51f0f0a

	if (r.type === "type" && noPrePostAutoLoaders) {
	continue;
	}

This PR also includes the snapshot that's generated when you run the test with these lines commented out.

Did you add tests for your changes?

This PR only contains tests, no implementation changes.

Does this PR introduce a breaking change?

No.

What needs to be documented once your changes are merged?

Documentation is unaffected.

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ezzatron / name: Erin (b6afa32)