The chrome.contentSettings API allows extension developers to provide alternative content settings controls than what Chrome is natively offering in chrome://settings/content. However, what limits its usability is that it doesn't cover all content setting types.

Improve the codebase so that developers who add content settings don't have to remember and take extra steps to wire new content setting types to the extensions API.

For example, ContentSettingsInfo could be extended with a new parameter determining whether this content setting is suitable to be exposed in the API. If yes, this content setting type should be wired to the API automatically.

We can also put additional hooks in the code (e.g. by setting up the OWNERship of affected files) to ensure that these changes also go through the API review.