keys tend to be organized (that's a horrible word for whatt he registry is lol) in a handful of locations depending on context. so those chrome keys are next to the other chrome keys. in enterprise we mod that area pretty often.

the 2 was to discover a new key are:

1. reg watcher that takes a baseline, then you install soemething, and you see the diff.
2. in the case of no new key has been added (like for this new setting), most softwares have support articles aimed at Enterprise Admins who need to control deployments granularly. So the regkeys tend to be available.

Sometimes some dev figures it out, sometimes word spreads from the devs themselves on Discord/etc. Sometimes if you contact Support they have that workaround (after escalating to engineer). Not that you can easily get to Google Engineers, but you have a much better track with say a paid Workspace account.

It's a FT job though to maintain a set of controlled software in an enterprise environment. Constant fiddling/tweaking. SOmetimes it's a RegKey, sometimes a GPO setting, sometimes you're modding a config file in AppData, or adding some lines to a Logon Script. And a lot of the info spreads by word of mouth still and to really answer your question - sometimes, no one knows where the hell it came from but after days of searching, you're happy some random forum post finally worked and you hope to never have to touch it again. Then you close your ticket and move on to the next one.

I don't miss it lol