Protect non-embedded clients from site client configuration settings

[mkdir-washington-edu]

Problem As we work on a custom theme and custom settings for the bioRxiv project (such as not showing the "create new private group" button in https://github.com/hypothesis/client/issues/7078 and calling annotations "comments" in https://github.com/hypothesis/client/issues/7065), we need to make sure that non-embedded clients (chrome extension, bookmarklet, Via) are still able to display all of the normal Hypothesis options, such as group selection, creating new groups, etc.

Solution The client configuration settings used on a page with an embedded client should not affect other, non-embedded clients. This will prevent site owners from using client configuration settings to, for example, cut off access to the Public group over their sites. It will also allow the bioRxiv TRIP project (which relies on multiple publisher groups) to continue working as normally while also still supporting the new ReviewR theme.

[robertknight]

When I raised this yesterday I forgot that we do actually have some existing mechanisms in this area. Each defined setting has an allowInBrowserExt flag which specifies whether the browser extension respects the setting. See https://github.com/hypothesis/client/blob/069eba5ed17982ea97c0536b4ad6c4e028b69281/src/annotator/config/index.ts#L91 for which settings have this flag enabled.

We'll need to review/extend this in some way for this project.