Add test coverage to ensure scanner-profiles and site-profiles return 404 when edited with a non-existing id
The following discussion from !41255 (merged) should be addressed:
-
@ashmckenzie started a discussion: suggestion: We should probably have coverage for editing a non-existing scanner profile ID.
This also applies to https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/requests/projects/security/dast_site_profiles_controller_spec.rb, since the scanner-profiles work is based on it and the two behave very similarly.
Edited by Paul Gascou-Vaillancourt