Add more debugging scenarios for not scaling as expected

[OfficiallySomeGuy]

Reference kedacore/keda#5263, adding some more documentation for guiding debugging, and highlighting known issues.

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)

Fixes #

Update docs adding more scenarios for debugging

[netlify]

✅ Deploy Preview for keda ready!

Name	Link
🔨 Latest commit	f033d28
🔍 Latest deploy log	https://app.netlify.com/sites/keda/deploys/65aab9ed5eb995000990e917
😎 Deploy Preview	https://deploy-preview-1298--keda.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

• Add your contribution to all applicable KEDA versions
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

• How to become a listed end-user or a listed commerical offering
• Our contribution guide

[tomkerkhove]

I personally would prefer a seperate item for this; people using pausing will more likely be helped faster if we have a dedicated item.

You can still refer to the new item from within the paused entry

[zroubalik]

Agree a separate section would be great

[zroubalik]

@OfficiallySomeGuy any update on this please?

[OfficiallySomeGuy]

@zroubalik unfortunately I am prohibited from making any further contributions, however if you would like to amend this PR and merge it, I would be supportive

[jpriebe]

Please get this merged into the documentation. We have wasted a lot of time trying to figure out why our deployment is not scaling to the desired value in specified in our cron trigger.

I know this is technically a feature of the HPA controller, but the keda docs really need prominent mentions of this throughout the documentation.