fix: don't clean up previous browser versions

[OrKoN]

Since we moved to the central binaries cache it does not make sense to clean up old binaries automatically because multiple installations can use different versions. We expect the users to clean the cache from time to time until we offer a CLI for managing the browsers.

Closes #9533

[Lightning00Blade]

Maybe we should add a log for the number of revisions being stored. That way the user easily see how many revisions they have saved and act upon that if need be.

[OrKoN]

@Lightning00Blade added a log message.

[q--]

So I saw this in the release notes, and it is not clear to me whether this applies to all of puppeteer or only to puppeteer-core. (I'm using the former.)

Does the puppeteer package still clean up old Chromium versions, or do I have to start cleaning them up myself so my disk won't fill up with unused Chromium installations? And if it's the latter, is there any (official or recommended) way to automate it?

[jacobg]

I was having this error for revision 1069273, then bumped to puppeteer 19.6.2, deployed to Google Cloud Function, and the error went away. Then a little later I did another deployment for an unrelated reason, and the error came back again on a new revision 1083080.

So it doesn't seem that 19.6.2 fixes the issue.