Support to Yarn v2/berry for webpacker 5.x

[pedrofurtado]

@gauravtiwari 👋

Closes #2888.

Clone of #2799 to provide support of Yarn v2 in 5.x versions of webpacker.

[pedrofurtado]

@gauravtiwari It worked like a charm! 🎉

PS: There are some errors in CI, but is not related to source code of PR, is related to some ruby version installed during build process 👍

[pedrofurtado]

@gauravtiwari Happy to see your review/suggestions on it 🎉 🥇

[merobal]

Do you have any plan to release this? @pedrofurtado @gauravtiwari

[pedrofurtado]

Hi @merobal ! 👋 Yes, asap we will prepare a 5.x release 🎉

[jerrod]

@pedrofurtado any chance this updated release will happen reasonably soon?

[SampsonCrowley]

@pedrofurtado was this released? I'm still seeing this on latest 5.x (5.4.3) more than 5 months later

[SampsonCrowley]

Nevermind, ignore me. I thought the version lock said <= 3

which why are we putting a maximum version on the new flags anyways? this is just going to keep needing to be rolled out every time, because when a new yarn version is released, the commands will revert to v1, instead of trying to assume compatibility with the most up-to-date api first

[SampsonCrowley]

And ignore me again, the issue above is with sprockets, not with the engine lock. running assets:precompile still attempts to trigger sprockets, even if sprockets is not enabled or installed on an app apparently