<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=214032) </details> <!--IssueSummary end--> ## Context (Follow up from https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27120) ## Description When moving the `ee_mr_widget_options_spec` over to Jest, we noticed that this is a **huge** spec file and a lot of the individual specs are bumping into each other. We could try to just clean up the specs, but part of this is caused by a very large and complex component. Let's clean up the component **and** the specs! Here's some ideas: - Move the call to `MRWidgetService.fetchInitialData()` out of the component and into `app/assets/javascripts/vue_merge_request_widget/index.js`. This way we won't be managing state and asynchronous events in our component tests. - Instead of having the EE `MrWidgetOptions` component extend the CE one, let's see if we can have it **compose** the CE one :thinking: