Docs: Review outdated screenshots in AST documentation

• Start this issue's title with Docs: or Docs feedback:.

Problem to solve

Some of the product screenshots in application security testing documentation are out of date. This can be confusing for users who reference the documentation and then compare what they see in GitLab.

Further details

Images to review:

./detect/security_scan_results.md:
  Line 75:![Security scanning results in a merge request](img/mr_security_scanning_results_v14_3.png)

./coverage_fuzzing/_index.md:
  Line 344:![Coverage Fuzzing Security Report](img/coverage_fuzzing_report_v13_6.png)

./dependency_scanning/_index.md:
  Line 80:![Dependency scanning Widget](img/dependency_scanning_v13_2.png)

./api_security_testing/configuration/enabling_the_analyzer.md:
  Line 362:![Edit collection variable tab View](../img/dast_api_postman_collection_edit_variable_v13_9.png)
  Line 366:![Edit environment variables View](../img/dast_api_postman_environment_edit_variable_v13_9.png)
  Line 370:![Edit request using variables View](../img/dast_api_postman_request_edit_v13_9.png)

./cve_id_request.md:
  Line 47:   ![CVE ID request button](img/cve_id_request_button_v13_4.png)
  Line 60:   ![New CVE ID request issue](img/new_cve_request_issue_v14_4.png)

./policies/scan_execution_policies.md:
  Line 263:![A diagram showing how scheduled security scans are processed and executed with potential delays.](img/scheduled_scan_execution_policies_diagram_v15_10.png)

./policies/_index.md:
  Line 501:     ![Policy Editor Rule Mode](img/policy_rule_mode_v15_9.png)
  Line 507:     ![Policy Editor YAML Mode](img/policy_yaml_mode_v15_9.png)

./api_fuzzing/create_har_files.md:
  Line 247:![Authorization token edited in Visual Studio Code](img/vscode_har_edit_auth_header_v13_12.png)

./api_fuzzing/configuration/enabling_the_analyzer.md:
  Line 431:![Edit collection variable tab View](../img/api_fuzzing_postman_collection_edit_variable_v13_9.png)
  Line 435:![Edit environment variables View](../img/api_fuzzing_postman_environment_edit_variable_v13_9.png)
  Line 439:![Edit request using variables View](../img/api_fuzzing_postman_request_edit_v13_9.png)

./troubleshooting_application_security.md:
  Line 79:![Incorporate target branch changes](img/outdated_report_branch_v12_9.png)
  Line 87:![Run a new pipeline](img/outdated_report_pipeline_v12_9.png)

./vulnerability_report/_index.md:
  Line 522:![Operational Vulnerability Tab](img/operational_vulnerability_tab_v14_6.png)

./vulnerabilities/_index.md:
  Line 518:![Create merge request from vulnerability](img/create_mr_from_vulnerability_v13_4.png)

./container_scanning/_index.md:
  Line 65:![Container Scanning Widget](img/container_scanning_v13_2.png)

Proposal

1. Review all screenshots in the doc/user/application_security directory from GitLab versions < 16.
2. For each of the screenshots found from step 1, remove or update them.

Who can address the issue

Anyone familiar with GitLab's application security testing features.

Other links/references