Supporting fallbacks for NativeMessagingHosts entries

As you may be aware, Windows desktop applications - to communicate with extensions in Chromium based browsers - utilise the https://developer.chrome.com/docs/apps/nativeMessaging/ protocol.

They therefore have to add registry keys to support NativeMessagingHosts with - however, most applications do this on a “known browser” basis and therefore if they aren’t aware of Brave, then Brave will not be compatible with that application (I’m specifically think of the problem I’ve had getting the Mailvelope extension from https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke working with gpgme).

Microsoft Edge addresses this issue by searching other applications (such as Chromium and Chrome) for entries as detailed on https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/native-messaging?tabs=windows .

Would it be possible for Brave to do a similar search for entries?