Improve the Testcase Issue Reporter issue titles

@meks suggested some improvements to the naming convention for test report issues: https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/187#note_307295698

Proposing instead of

Results for ./qa/specs/features/browser_ui/7_configure/kubernetes/kubernetes_integration_spec.rb | Configure Kubernetes Cluster Integration Project Clusters can create and associate a project cluster

It should be

relative_test_file_path | test_case_name_in_code_ (and the Enterprise Edition label for EE tests)

We drop Results for and the start of the path that is always the same.

So the example above would be

browser_ui/7_configure/kubernetes/kubernetes_integration_spec.rb | Configure Kubernetes Cluster Integration Project Clusters can create and associate a project cluster

And an EE test example, where the full path is qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:

browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb | Create Restricted protected branch push and merge when only one user is allowed to merge and push to a protected branch behaves like only user wi... Enterprise Edition

TODO:

• Update the testcase issue reporter to use the new title format gitlab-org/gitlab-qa!426 (merged)
• Write a script to update the titles of the existing issues
• Run the update script as soon as the new reporter is released
• Check that all scheduled pipelines use the updated reporter and the new title format