Update yarn lockfile

What does this MR do and why?

The yarn lockfile keeps updating for me when I run yarn locally. This MR contains the changes

added frontend tooling (archive) labels

assigned to @pslaughter

	1 Warning
	This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
frontend	Florie Guibert (@fguibert) (UTC+10, 16 hours ahead of @pslaughter)	Vitaly Slobodin (@vitallium) (UTC+3, 9 hours ahead of @pslaughter)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

@mikegreiling do you want to be maintainer reviewer here which updates yarn.lock so that yarn install doesn't trigger a change? This doesn't solve the problem why master isn't failing. Just updates the yarn.lock file.

/cc @leipert

requested review from @mikegreiling

Oh! There's already an MR for this !80644 (merged)

Closing...

closed

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits 7bb0d54a and 66800d2e

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	3.66 MB	3.66 MB	-	0.0 %
mainChunk	2.29 MB	2.29 MB	-	0.0 %

---

Note: We do not have exact data for 7bb0d54a. So we have used data from: b711569d.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun the bundle-size-review job
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.

Please look at the full report for more details

---

Read more about how this report works.

Generated by Danger

Allure report

allure-report-publisher generated test report for 66800d2e!

review-qa-reliable: test report
review-qa-smoke: test report

added typemaintenance label and removed tooling (archive) label