Fixes #3005 Namespace our dependencies to prevent conflicts

[remyperona]

Fixes #3005 and closes #2126

Following issue #3003, and to prevent possible conflicts in the future, use Mozart to automatically import and namespace our dependencies.

Also regenerate the advanced-cache.php file on update to comply with the new path and name of the mobile detect library.

Imported Dependencies

• matthiasmullie/minify & matthiasmullie/path-converter (Minification library, used in other minification plugins)
• mobiledetect/mobiledetectlib (Mobile Detect library, very commonly used)
• wp-media/background-processing (WP Background Processing library, commonly used in various plugins)
• wp-media/rocket-lazyload-common (Used in WP Rocket and the lazyload plugin)

[hellofromtonya]

@Tabrisrp There are multiple places in Rocket where MatthiasMullie\Minify, MatthiasMullie\Minify\CSS, and MatthiasMullie\Minify\JS are imported including in the inc/Engine/Optimization and inc/Engine/Media folders.

Update: Whoops never mind. Those got fixed in commits that I hadn't pulled down yet. Doh.

[remyperona]

@hellofromtonya All of them should have been updated in this PR, I can't find any reference left when doing a search in the directory, can you?

[hellofromtonya]

@Tabrisrp Sorry about that. I hadn't pulled down the latest commits. Doh.

All good. 👍

[hellofromtonya]

@Davidacu This one is the last one for Alpha 3. It's ready for QA.

[Davidacu]

I ran into an error after doing composer install --no-dev

[Davidacu]

• Regression tests on Activation/Deactivation, Minification/Combine, Lazyload, Cache, Preload and Optimize CSS Delivery, Find the results attached, 99% pass rate, the failed case is known.
  testrail-report-21.pdf
• Installed with Woocomerce 4.4, all ok 👍
• Tested with Elementor plugin installed which loads WP_Background_Process , all ok 👍
• Tested with other plugins that make use of the imported dependencies such as Mobile detect and Fast velocity minify, all good 👍
• No notices or errors found in debug log.

[dodgepong]

@Davidacu Hey there, I ran into the same error today when installing with --no-dev. What did you do to resolve that?

[iCaspar]

@dodgepong If I recall correctly, when running with --no-dev you also need --no-scripts
We only run Mozart in development to create the package namespacing, not in production.

[dodgepong]

@iCaspar Thanks, that did it!