Fix vaadin latest dep test

[laurit]

Resolves #3782
Resolves #3781 (this one has one more failure, but it seems like a one time occurrence)

[trask]

can you add to this comment explaining this problem only affects our tests, and is not a problem for end users?

[laurit]

I would assume that it is a problem for at least some users GoogleChrome/workbox#2904 Our test isn't exactly a regular vaadin application. We let vaadin development mode generate a bunch of files each time test is first run after clean that regular users would add to version control. I suspect that the javascript tooling used probably doesn't attempt to find new package versions on each run so if they set up their project before yesterday this is yet to break for them (this is speculation). If it breaks they probably know how to pin package to working version. I also initially tried to make it use the previous working version of workbox-build but failed at it. I guess should have use pnpm-lock.yaml to pin version. So after failing with javascript tooling I turned to what I know, patching java code. As an alternative we could find the latest working vaadin version (something that uses workbox-webpack-plugin before 6.x?) and make latest dep tests use that until vaadin switches to workbox-webpack-plugin 6.2.
Edited: there is also a vaadin issue for this vaadin/flow#11524

[trask]

As an alternative we could find the latest working vaadin version (something that uses workbox-webpack-plugin before 6.x?) and make latest dep tests use that until vaadin switches to workbox-webpack-plugin 6.2.

I think this would be my preference