Gitlab::Checks is now instrumented

Paco Guzman requested to merge 22053-gitlab-checks-metrics into master

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?

What are the relevant issue numbers?

Relates #22053 (moved)

Merge request reports