[Bug]: Pint lint failure on CPUThrottlingHigh alert

[skl]

What happened?

Pint lint failure, the docs on this check can be found here:

• https://cloudflare.github.io/pint/checks/promql/fragile.html

Please provide any helpful snippets.

prometheus_alerts.yaml:342-346 Warning: Aggregation using `without()` can be fragile when used inside binary expression because both sides must have identical sets of labels to produce any results, adding or removing labels to metrics used here can easily break the query, consider aggregating using `by()` to ensure consistent labels. (promql/fragile)
 342 |     "expr": |
 343 |       sum(increase(container_cpu_cfs_throttled_periods_total{container!="", job="cadvisor", }[5m])) without (id, metrics_path, name, image, endpoint, job, node)
 344 |         /
 345 |       sum(increase(container_cpu_cfs_periods_total{job="cadvisor", }[5m])) without (id, metrics_path, name, image, endpoint, job, node)
 346 |         > ( 25 / 100 )
make: *** [Makefile:80: pint-lint] Error 1

Originating PR:

• Update CPUThrottlingHigh and KubeContainerWaiting alerts #942

What parts of the codebase are affected?

Alerts

I agree to the following terms:

• I agree to follow this project's Code of Conduct.
• I have filled out all the required information above to the best of my ability.
• I have searched the issues of this repository and believe that this is not a duplicate.
• I have confirmed this bug exists in the default branch of the repository, as of the latest commit at the time of submission.

[github-actions]

This issue has not had any activity in the past 30 days, so the
stale label has been added to it.

• The stale label will be removed if there is new activity
• The issue will be closed in 7 days if there is no new activity
• Add the keepalive label to exempt this issue from the stale check action

Thank you for your contributions!

[sleepyfoodie]

here's the issue created on pint for reference.