[JENKINS-68699] Upgrade Yarn from 1.22.19 to 3.2.0

[StefanSpieker]

Upgrade to yarn 3.0 and minor node update. Accoring to this issue we still need to install the latest 1.x release to use the 3.0 ...

Proposed changelog entries

• Internal: Upgrade to yarn 3.0

Proposed upgrade guidelines

N/A

Submitter checklist

• (If applicable) Jira issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are correct
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[StefanSpieker]

I think we should wait for eirslett/frontend-maven-plugin#1012

[basil]

I think we should wait for eirslett/frontend-maven-plugin#1012

@StefanSpieker eirslett/frontend-maven-plugin#1012 was released in 1.12.1, which we upgraded to in #6139.

[NotMyFault]

The outstanding blockers have been addressed by now, do you mind resolving the merge conflicts so we can pick the PR up for another review @StefanSpieker ?

[basil]

I resolved the hard/physical merge conflicts at least. There may still be soft/logical conflicts.

[basil]

I just pushed some commits that should complete this effort.

Didn't realize this was checking in a multi MB blob

[basil]

Oh dear, war/.yarn/releases/yarn-3.2.0.cjs is a 2.1 MiB file? And they want you to check this into your repository? I really dislike this. Not sure we want to do this. There has to be a better way.

[basil]

In commit b54f044 I found a trick to download Yarn Berry via Maven Antrun Plugin rather than Frontend Maven Plugin. If accepted, it is critical that this PR be squash merged to avoid bloating the repository size.

[timja]

I tested it out locally and all seems good

[NotMyFault]

Thanks for investigating into an alternative solution, basil, works out great so far when checking out locally.

---

Non blocking nit: berry 3.2.1 is out by now which we could use over 3.2.0.

[basil]

Non blocking nit

I am glad this is non-blocking, because I would decline to accommodate it after going above and beyond the expectations for a maintainer to the degree that I already have regarding this PR which I did not submit myself.

[basil]

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process. Thanks!

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[daniel-beck]

Renovate doesn't seem to like this in #6892.

[timja]

Renovate doesn't seem to like this in #6892.

I'll take a look, renovate definitely supports it

[timja]

looking at renovatebot/renovate#14797

[timja]

see renovatebot/renovate#15414

[basil]

I pushed commit 33ba459 to #6894 to make the hack even more gross to be able to support Renovate.

[Vlatombe]

Not sure this matters, but the antrun execution breaks offline usage.

[basil]

The antrun execution is a hack to work around eirslett/frontend-maven-plugin#1032. The long-term solution should be implemented in frontend-maven-plugin and would support offline usage.