## Why are we doing this work This follows up on @cam.x's comment in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63530#note_596539073: > I like that DAST code have space between each session, can we do that for fuzzing code as well We are looking at improving that API fuzzing configuration snippet that currently looks like this:  To have more options as to how the code snippet is formatted, we'll want to move its generation to the ~frontend. ## Relevant links - [Prior art](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52540) - [Similar implementation](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63530) - [Follow-up issue to remove the GraphQL field](https://gitlab.com/gitlab-org/gitlab/-/issues/342987) ## Non-functional requirements - [ ] Documentation: - [ ] Feature flag: - [ ] Performance: - [ ] Testing: ## Implementation plan - [x] Move the configuration template to the ~frontend. - [x] When saving the API fuzzing configuration, present the client-side template with the proper replacements. - [x] Remove the tip insertion helpers from the ~frontend(`ee/app/assets/javascripts/security_configuration/api_fuzzing/utils.js`). - [x] Mark the `apiFuzzingCiConfigurationCreate` mutation as deprecated. - [-] Remove the GraphQL mutation.