Add coverage fuzzing to registration features

What does this MR do and why?

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/377751

We want to add coverage-guided fuzz testing to features available to users who have service ping data sharing enabled.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

1. Testing previous behavior:
   • Make sure you're on an Ultimate plan Gitlab gdk instance
   • Using the guide here:
     • try checking the Security and Compliance > Security configuration > Coverage Fuzzing section of a project. This should show up as enabled or not enabled (but not "not available")
     • try setting up the .gitlab-ci.yml file so that it uses coverage fuzzing. This should set up a working pipeline
2. When registration features are enabled:
   • Make sure you're on a non-Ultimate plan Gitlab gdk instance (for example, remove current license or stub #plan to return STARTER_PLAN)
   • Make sure you have the registration features checkbox enabled (Admin -> Settings -> Metrics and profiling -> Usage statistics -> Enable Registration Features)
   • Using the guide here:
     • try checking the Security and Compliance > Security configuration > Coverage Fuzzing section of a project. This should show up as enabled or not enabled (but not "not available")
     • try setting up the .gitlab-ci.yml file so that it uses coverage fuzzing. This should set up a working pipeline
3. When registration features are disabled:
   • Make sure you're on a non-Ultimate plan Gitlab gdk instance
   • Make sure you have the registration features checkbox disabled (Admin -> Settings -> Metrics and profiling -> Usage statistics -> Enable Registration Features)
   • Using the guide here:
     • try checking the Security and Compliance > Security configuration > Coverage Fuzzing section of a project. This should show a prompt to update to Ultimate.
     • try setting up the .gitlab-ci.yml file so that it uses coverage fuzzing. This should not be working.
4. Make sure that the new text appears on the docs page:
   • run gdk restart gitlab-docs
   • go to _local_gitlab_docs_host_/ee/user/admin_area/settings/usage_statistics.html#registration-features-program and make sure the new section is on the page and the link works

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.