[BUG] Add resolved paths to app-code babel compile

[maschwenk]

After we split the node_module compiling from the app code compiling, we left out resolved_paths. I first noticed this after I upgraded to v4.0.0.rc.3 from v4.0.0.rc.2.

This commit has now created the whitelist of node_module compiled code, which left my resolved_paths out of the loop (neither compiled by accident by the old node_module config, nor compiled by the babel config because it only looks at the source_path)

For people providing resolved_paths != []

I realize not every project is using resolved_paths but without this you get very confusing errors if your source_path code is depending on resolved_path code. I think whatever performance penalty you get from this should be expected given it's clearly stated that resolved_paths are not-ideal elsewhere.

It's hard to imagine this would be unexpected/unwanted for people specifying resolved_paths because it was probably happening in Webpacker 3.x anyway

For people providing resolved_paths === []

For people not using resolved_paths this will have no effect.

[javan]

Thanks!