feat: add USB protected classes handler

[jkleinsc]

Description of Change

• When I implemented WebUSB in feat: add support for WebUSB #36289, I carried over logic from the chromium implementation which determines if access should be given to protected USB classes under certain circumstances. Instead of doing this we should instead add a handler to allow Electron developers to programmatically determine which protected classes should be allowed. By default (eg if a handler is not defined), the default list of protected classes will be prevented from access via WebUSB.
• This is a followup/refactor of feat: allow access to protected usb classes from webusb #38155 to address security concerns raised in that PR.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• relevant documentation, tutorials, templates and examples are changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Added setUSBProtectedClassesHandler to allow access to protected USB classes with WebUSB.

[zcbenz]

API LGTM

[nikolaxmarkovic]

Would it be ok to port change to 24-x-y and\or 25-x-y since branches include #36289 ?

[codebytere]

API LGTM

[release-clerk]

Release Notes Persisted

Added setUSBProtectedClassesHandler to allow access to protected USB classes with WebUSB.

[trop]

I was unable to backport this PR to "24-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I have automatically backported this PR to "25-x-y", please check out #38493

[trop]

@jkleinsc has manually backported this PR to "24-x-y", please check out #38498