Bumped webpack to v5

[valadas]

Bumped webpack to v5

This removes the workarounds put in place in 9.11.1 so the build works in CI where node was upgrade to v18. Our build should now work on node 16 and 18 without workaround in place... Hopefully.

I tested a full build and confirmed all the modules still load up fine.

[valadas]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[valadas]

I don't get it, the build error has nothing to do with these changes... @bdukes do you have any clue about the binlog version (assuming that is the problem here)...

[valadas]

Adding the nuget package appears to fix it.

[david-poindexter]

@valadas this looks great! One question. I see the webpack script (which uses webpack-dev-server ...) has been removed from all the package.json files. What is replacing this? Are we recommending just using the webpack CLI now for this? If so, do the Cake scripts need to be up updated accordingly? (I honestly can't remember if those used this or not in the scoped build options.)

[valadas]

It was because since we have yarn start --scope something now (which we did not have back then, using the webpack task is more complex and needs the developer to setup the view to load from :8080 manually which we don't have anywhere in our docs and many already have something running on 8080 and then get into troubles, etc. Happy to bring it back if anyone mentions they actually use that task...

[david-poindexter]

It was because since we have yarn start --scope something now (which we did not have back then, using the webpack task is more complex and needs the developer to setup the view to load from :8080 manually which we don't have anywhere in our docs and many already have something running on 8080 and then get into troubles, etc. Happy to bring it back if anyone mentions they actually use that task...

That makes perfect sense - thanks for the explanation. And seriously...thank you for this PR!