Gitlab::Checks is now instrumented

What does this MR do?

Instrument Gitlab::Checks like ForcePush, ChangeAccess and MatchingMergeRequest to have a better insight in what is happening, currently Gitlab::GitAccess#change_access_check for example is not enough

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• CHANGELOG entry added
• [ ] Documentation created/updated
• [ ] API support added
• Tests
  • [ ] Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if you do - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Relates #22053 (moved)