Update coverage fuzzing docs and enable flag

* Add screnshots
* Add updated docs and links

config/feature_flags/development/coverage_fuzzing_mr_widget.yml

@@ -4,4 +4,4 @@ introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43545
 rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/257839
 type: development
 group: group::fuzz testing
-default_enabled: false
+default_enabled: true

doc/user/application_security/coverage_fuzzing/index.md

@@ -17,6 +17,22 @@ and your own test processes. If you're using [GitLab CI/CD](../../../ci/README.m
 you can run your coverage-guided fuzz tests as part your CI/CD workflow. You can take advantage of
 coverage-guided fuzzing by including the CI job in your existing `.gitlab-ci.yml` file.
 
+![Coverage Fuzzing Security Report](img/coverage_fuzzing_report_v13_6.png)
+
+By clicking on one of the detected vulnerabilities, you can
+see the details.
+
+![Coverage Fuzzing Vulnerability Modal](img/coverage_fuzzing_vuln_modal_v13_6.png)
+
+## Security Dashboard
+
+The [Security Dashboard](../security_dashboard/index.md) shows you an overview of all
+the security vulnerabilities in your groups, projects and pipelines.
+
+## Interacting with the vulnerabilities
+
+After a vulnerability is found, you can [interact with it](../index.md#interacting-with-the-vulnerabilities).
+
 ## Supported fuzzing engines and languages
 
 GitLab supports these languages through the fuzzing engine listed for each. We currently provide a
@@ -222,6 +238,7 @@ This essentially creates two steps:
 
 The `covfuzz-ci.yml` is the same as that in the [original synchronous example](https://gitlab.com/gitlab-org/security-products/demos/coverage-fuzzing/go-fuzzing-example#running-go-fuzz-from-ci).
 
+
 ### Glossary
 
 - Seed corpus: The set of test cases given as initial input to the fuzz target. This usually speeds

ee/app/controllers/ee/projects/merge_requests_controller.rb

@@ -11,7 +11,7 @@ module EE
         before_action only: [:show] do
           push_frontend_feature_flag(:anonymous_visual_review_feedback)
           push_frontend_feature_flag(:missing_mr_security_scan_types, @project)
-          push_frontend_feature_flag(:coverage_fuzzing_mr_widget, @project)
+          push_frontend_feature_flag(:coverage_fuzzing_mr_widget, @project, default_enabled: true)
         end
 
         before_action :whitelist_query_limiting_ee_merge, only: [:merge]

ee/app/views/projects/merge_requests/show.html.haml

@@ -20,4 +20,4 @@
     window.gl.mrWidgetData.sast_comparison_path = '#{sast_reports_project_merge_request_path(@project, @merge_request) if @project.feature_available?(:sast)}'
     window.gl.mrWidgetData.dast_comparison_path = '#{dast_reports_project_merge_request_path(@project, @merge_request) if @project.feature_available?(:dast)}'
     window.gl.mrWidgetData.secret_scanning_comparison_path = '#{secret_detection_reports_project_merge_request_path(@project, @merge_request) if @project.feature_available?(:secret_detection)}'
-    window.gl.mrWidgetData.coverage_fuzzing_comparison_path = '#{coverage_fuzzing_reports_project_merge_request_path(@project, @merge_request) if @project.feature_available?(:coverage_fuzzing) && Feature.enabled?(:coverage_fuzzing_mr_widget, @project)}'
+    window.gl.mrWidgetData.coverage_fuzzing_comparison_path = '#{coverage_fuzzing_reports_project_merge_request_path(@project, @merge_request) if @project.feature_available?(:coverage_fuzzing) && Feature.enabled?(:coverage_fuzzing_mr_widget, @project, default_enabled: true)}'