Migrate build process to Yarn

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.1.X, 7.2.X, Master
• Component/s: ~ [Archived] Frontend Infrastructure
• Labels:
  • liferay-dxp-72-sp1
  • liferay-fixpack-dxp-2-7210
  • pt-app-security-review
• Branch Version/s:
  7.2.x, 7.1.x
• Backported to Branch:
  Committed
• Epic Link: fi-build-process-performance
• Sprint: S02E10 - Fight Club
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/69997
• QA Test Name:
  • LocalFile.ContentPagesWithSearch#FilterByPageFacet
  • LocalFile.ContentPagesWithSearch#SearchEditableText
  • LocalFile.ContentPagesWithSearch#SearchStaticText
  • LocalFile.ExportImport#ExportImportPrivatePage
  • LocalFile.FjordTheme#AddThemeSite
  • LocalFile.Forms#AddFormInGlobal
  • LocalFile.LocalizationWithWebContentUI#AddWCWithTranslation
  • LocalFile.PorygonTheme#AddThemeSite
  • LocalFile.UIInfrastructureUsecase#RightToLeftSmoke
  • LocalFile.WesterosTheme#AddThemeSite
  • LocalFile.WidgetPagesUseCase#SitesPrivatePagesPermissions
• QA Test Score: 55

To speed up development and have a better control of the project dependencies, we should try to move to Yarn+Workspaces to make sure as many dependencies as possible are shared and the node_modules footprint is reduced.

Having a single point to analyze dependencies (yarn.lock) also contributes to improve control and visibility over what's being used and why, while making it simpler to make broad infrastructure build changes.