Update Storybook module settings stories to use createLegacySettingsWrapper

Bug Description

Currently our Storybook stories for module settings each use the same Settings wrapper component which is used just for rendering in Storybook. This is defined in the stories file for multiple modules’ settings stories, e.g.:

https://github.com/google/site-kit-wp/blob/33a649d3b20fbcf9f5d9f04d6ff53640825a8e41/stories/module-analytics-settings.stories.js#L56-L103

In #1715 we introduced the createLegacySettingsWrapper utility for reducing this boilerplate needed for each module’s settings stories.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• Settings wrapper components defined in stories/module-*-settings.stories.js files should be removed
• Stories in stories/module-*-settings.stories.js should be refactored to use createLegacySettingsWrapper

See Tag Manager for example usage: https://github.com/google/site-kit-wp/blob/20f826af64092da7633d94ead7d23a75667762a7/stories/modules-tagmanager-settings.stories.js#L35

Implementation Brief

• Update stories/module-*-settings.stories.js (except tagmanager as it is already done) to use the new utility instead of the inline Settings component definition

QA Brief

• N/A

Changelog entry

• N/A

[felixarntz]

IB ✅

[umuur]

Hello, can I take this issue as a first timer?