Add metrics for BitBucket and GitHub API calls

What does this MR do?

Currently, we don't know anything about how many calls are we doing and how much time they take. This MR adds some metrics.

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, if necessary
• 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 it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

assigned to @smcgivern

approved this merge request

enabled an automatic merge when the pipeline for 96fded62 succeeds

Good call, thanks @vsizov! Should we pick into 9.5?

@smcgivern That would be cool!

• @stanhu
• @smcgivern
• @jivanvl and @psimyn

This is completely harmless, but lets us see data in grafana sooner.

/milestone %"9.5" 
/label ~"Pick into Stable" 

Looks good to me.

Ping @jivanvl @psimyn

merged

mentioned in commit 95ead8b1

Thanks for the ping, but remember folks assign the proper milestone and labels!

changed milestone to %9.5

added Pick into Stable label

Picked into https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2698, will merge into 9-5-stable-ee ready for 9.5 RC5

removed Pick into Stable label

mentioned in commit 168caf55

@jivanvl I was leaving that until it was approved

Okay I approved and it's picked as well