As of now, CommunityConfiguration expects the set of configuration options is equal at all projects where it is enabled. The only thing that controls which features are displayed in the dashboard, and what configuration options display in the configuration editor, is which extensions are installed on the wiki. For example, if #growthexperiments is installed, then Special:CommunityConfiguration will display //all// possible configuration for GrowthExperiments, including options for feature that is not enabled at that project (and including options for features that are not even //available// at that project).
Within this task, we should hide unavailable features from Special:CommunityConfiguration, since it makes no sense to configure them when not available. See Acceptance Criteria for a list.
==== Acceptance Criteria
**Newcomer onboarding:**
[ ] Given //Personalized praise// is not available on a wiki, When I view Special:CommunityConfiguration/Mentorship, Then I do not see any Personalized praise settings.
**Suggested edits**
[ ] Given //Add a Link// is not available on a wiki, When I view Special:CommunityConfiguration/GrowthSuggestedEdits, Then I do not see any Add a Link settings.
[ ] Given //Add an image to an unillustrated article// is not available on a wiki, When I view Special:CommunityConfiguration/GrowthSuggestedEdits, Then I do not see any //Add an image to an unillustrated article// settings.
[ ] Given //Add an image to an article section// is not available on a wiki, When I view Special:CommunityConfiguration/GrowthSuggestedEdits, Then I do not see any //Add an image to an article section// settings.