chore: Remove sidekiq thread contention from capacity planning

Furhan Shabirrequested to merge
chore/exclude-sidekiq-from-thread-contention-saturation-predictions into master

What

Remove sidekiq thread contention from capacity planning

Why

We have sidekiq_shard_workers saturation point to detect if we are saturating on available sidedkiq worker capacity, which implicitly tells about the thread saturation per pod and hence this sidekiq_thread_contention is redundant.

Discussion thread: https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/2029#note_2820226476

Merge request reports