Update test case links in create issue spec

What does this MR do?

Update test case links in:

• create issue spec: gitlab-org/quality/testcases#1792 (closed)
• create issue spec: gitlab-org/quality/testcases#1793 (closed)
• clone_push_pull_project_snippet_spec: gitlab-org/quality/testcases#1794 (closed)

Due to errors in reporting

Gitlab::Error::BadRequest Server responded with code 400, message: 400 Bad request - Note {:base=>["Maximum number of comments exceeded"]}. Request URI: https://gitlab.com/api/v4/projects/gitlab-org%2Fquality%2Ftestcases/issues/1085/notes

Gitlab::Error::BadRequest Server responded with code 400, message: 400 Bad request - Note {:base=>["Maximum number of comments exceeded"]}. Request URI: https://gitlab.com/api/v4/projects/gitlab-org%2Fquality%2Ftestcases/issues/1167/notes

Gitlab::Error::BadRequest Server responded with code 400, message: 400 Bad request - Note {:base=>["Maximum number of comments exceeded"]}. Request URI: https://gitlab.com/api/v4/projects/gitlab-org%2Fquality%2Ftestcases/issues/832/notes

Check-list

• General code guidelines check-list
  • Code review guidelines
  • Style guides
• Quarantine test check-list
  • Follow the Quarantining Tests guide.
  • Confirm the test has a quarantine: tag with the specified quarantine type.
  • Note if the test should be quarantined for a specific environment.
• Dequarantine test check-list
  • Follow the Dequarantining Tests guide.
  • Confirm the test consistently passes on the target GitLab environment(s).
    • (Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE variable from the package-and-qa job of the current merge request.
• To ensure a faster turnaround, ask in the #quality Slack channel for someone to review and merge the merge request, rather than assigning it directly.