That approach is fragile, because it won't stop applying the crazy workaround after Chrome version Y fixes the problem.
You can't know which version it's going to be, and there's a chance you won't be maintaining that code anymore then.
I appreciate the idealism of "if your standard's compliant site doesn't work in Chrome 142 then it's Google's problem" but I can't just throw up my hands and let my site be broken.
The User Hints spec specifically says that user agents aren't required to provide them in all circumstances, and that they shouldn't be provided in some.
> User agents ought to exercise judgement before granting access to this information, and MAY impose restrictions above and beyond the secure transport and delegation requirements noted above.
The message from Google is clear: Whilst we understand you want to work around bugs, and this is the only way to do it, you really should be second-guessing whether you need to touch this API at all.
user agent prefers a "mobile" user experience.
UA Client Hints will provide: brand, major version, full version, platform brand and architecture, platform architecture, model and whether it should be treated as a mobile platform.
If you were using the UserAgent to guess if the browser was a particular version with a particular bug, now you don't have to parse something and probably get it wrong.
It seems you are using "Mozilla 5.0". Your browser is really out of date!
Please consider updating to rand("Googlebot/2.1", "Version/7", "XUL/97", "HTML/5").
> User agents ought to exercise judgement before granting access to this information, and MAY impose restrictions above and beyond the secure transport and delegation requirements noted above.
Hard problems are hard, but my experience, and the recommended approach by browser implementers, is that feature detection works better.