chore: implement no-op chrome.action extension APIs

[codebytere]

Description of Change

Refs #36545.
Refs #40142.

Implement scaffolding for unsupported chrome.action API surface. From documentation:

You can use the chrome.action API to control the toolbar button for your extension in Chrome's UI. The action icons are displayed in the browser toolbar, to the right of the omnibox (on left-to-right devices). After installation, by default, these appear in the extensions menu (the puzzle piece). Users can choose to pin your extension icon to the toolbar.

Electron has no comparable concept for the toolbar button or popup, and will never support this API. However, as of now, many extensions use it, and it throws disruptive errors that can prevent other supported aspects of a given extension from working as intended. To combat this, I'm adding stripped-down infrastructure for the API without supporting it, such that it will not throw an error when chrome.action APIs are called but will log that the APIs are unsupported and will not work as expected. This will prevent confusing errors for users and more clearly delineate what we do and don't support.

This approach was also taken in this PR.

Checklist

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

Release Notes

Notes: none.

[release-clerk]

No Release Notes

[trop]

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

[trop]

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

[trop]

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

[patil-milind]

In which Electron version this change will be available for testing?