Updating to JQuery 3.6.0

[HermesSbicego-Laser]

For dev branch, we will update JQuery to its latest stable release (3.6.0.)

[HermesSbicego-Laser]

Working on this, we found the the gulp pipeline is broken.
what we see installing it, it's that package has lots of vulnerabilities (2 low, 10 moderate, 19 high, 4 critical) and some dependencies are deprecated.
installing new versions and new dependencies results in a not working gulp.js file.
So the question is: should we use gulp anymore?
We suggest and we will work on porting the gulp pipeline to this VS extension https://marketplace.visualstudio.com/items?itemName=MadsKristensen.BundlerMinifier, https://www.talkingdotnet.com/gulp-is-no-longer-default-choice-asp-net-core/
We use it in our solutions and it works as expected.

[Skrypt]

If I remember correctly, Orchard used to use BundlerMinifier and got migrated to the gulp pipeline because we could fine-tune it more. There are also dependencies that only need to be copied without getting bundled so the gulp pipeline can also do that.

Moving back to the BundlerMinifier won't fix the deprecated dependencies issue either. So, I believe this would be more regression than anything. I would try to fix the npm packages and dependencies before anything else. Because in the end, that's what's needed.

[HermesSbicego-Laser]

Thanks @Skrypt for clarifying why gulp was choosen.
So, we will try to update and keep gulp pipeline. Any help will be appreciated.

[MatteoPiovanelli-Laser]

@Skrypt
Based also on your comments in #8522, what would you recommend?
We think the pipeline should be updated to a state where it works "out of the box", and it possibly easy to set up for new and custom modules/themes.

[Skrypt]

What would need to be done is to use the latest LTS version of Node.js + npm and update the packages.json files up until no package deprecated are found. After that, test things manually in OC to make sure the components are still working. Because it can "transpile" without necessarily working.

That's why I said earlier that normally using the Node.js version that was used back then to transpile everything should be the easiest way to make it transpile and work.

[Skrypt]

Also as part of being able to do reproducible builds, I think we should document the version of Node.js used to transpile the Gulp pipeline to avoid having this situation again in a few years. The recommendation is good for Orchard Core too.