MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description This is a follow up to this discussion here: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/192698#note_2549427682 We would like to add some preStart events to our remote development fixture files for completeness since we already include postStart events. <!-- TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance" --> <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria - [ ] Add preStart event to `ee/spec/fixtures/remote_development/example.devfile.yaml.erb` - [ ] Add preStart event to other fixtures where needed - [ ] Update the `workspace_deployment` method in `remote_development_shared_contexts.rb` to return the expected configuration including the preStart event we added to the fixture - [ ] Make sure the smoke-test-suite passes ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->