Add status_issue rspec tags for manage tests

What does this MR do?

Part of https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/504

• If a test includes shared examples, the status_issue tag is assigned to the parent context, not the example definition.
• If there are multiple shared examples or created multiple tests dynamically, no status_issue tag is assigned because there's no 1:1 relationship. See https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/504#note_398484646

Spec files without status_issue tags assigned:

• qa/qa/specs/features/browser_ui/1_manage/project/protected_tags_spec.rb
• qa/qa/specs/features/ee/browser_ui/1_manage/group/group_file_template_spec.rb

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team