What do we do about these kinds of situations/this specific case?
On the broader side of things, it's exactly the same as any other question, just a little more urgent. Deal with them. Get them answered, and closed, and dealt with as quickly as possible.
The quicker we have a body of material that actually deals with the problem, or let's people know what's going on, the quicker Google will start returning those things when people search for the errors they see. Even if you vote to close (dupe), leaving extra comments can help people while it's being closed, even duplicate answer in a complex situation. The system isn't going to explode.
Everything we do here —not just surge situations— isn't just to help one person, it's to help the next ten people with the same problem. It's to deduplicate the effort at both ends of the problem.
In a surge, the tail, the time our answers will help is short but we have to act really quickly to avoid lots of people having to hunt for the answer, ask duplicate questions, and leave us with even more work to answer them.
In this case, I'd be tempted to butcher the title on the canonical answer thread so it's clear this is a "June 2022" problem that's being described, but I'd leave that until after it's resolved maybe? Who knows.