Route both CTAs through CommunityConfiguration with the change pre-staged.

The CTA link takes the sysop to the CommunityConfiguration edit surface for the opt-in schema with either (a) a new entry staged for addition — the QID they were previewing, a sensible default local title (e.g. the Wikidata label in the wiki's content language, which the sysop can adjust before saving), and an empty rationale — in the activate case, or (b) the matching entry staged for removal in the deactivate case. This relies on CommunityConfiguration supporting a URL-driven staged-edit mechanism; if CommunityConfiguration does not currently support this, it is a dependency on the CommunityConfiguration team (or an upstream contribution WE2 may need to make) and must be flagged as such in M2's initial sprint planning rather than discovered mid-implementation.