Support profiling for keda components

[yuvalweber]

Provide a description of what has been changed

Checklist

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

Fixes kedacore/keda#4789

[netlify]

✅ Deploy Preview for keda ready!

Name	Link
🔨 Latest commit	ed28616
🔍 Latest deploy log	https://app.netlify.com/sites/keda/deploys/65315839549ef700081cdbf2
😎 Deploy Preview	https://deploy-preview-1250--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

[yuvalweber]

Done 👍

[tomkerkhove]

Thanks for adding this! But this page is automatically updated and you need to create a new file under https://github.com/kedacore/keda-docs/tree/main/content/troubleshooting

[tomkerkhove]

You can see in the preview why: https://deploy-preview-1250--keda.netlify.app/docs/2.13/troubleshooting/

[yuvalweber]

Hey @tomkerkhove not sure I understand.
Should I delete this file under the 2.13 and just add a new file under the main one?

[zroubalik]

Thanks for adding this! But this page is automatically updated and you need to create a new file under https://github.com/kedacore/keda-docs/tree/main/content/troubleshooting

@tomkerkhove actually I think that we should change this approach and have a specific content for each version. For example the stuff added in this PR is only valid on versions 2.13+ and also in the current apporach we can't get links to the specific topics in the guide.

[tomkerkhove]

Thanks for adding this! But this page is automatically updated and you need to create a new file under main/content/troubleshooting

@tomkerkhove actually I think that we should change this approach and have a specific content for each version. For example the stuff added in this PR is only valid on versions 2.13+ and also in the current apporach we can't get links to the specific topics in the guide.

I think we should fix how the troubleshooting widgets are added to be per version, but do think they should all be in separate files as we have it today

[zroubalik]

Thanks for adding this! But this page is automatically updated and you need to create a new file under main/content/troubleshooting

@tomkerkhove actually I think that we should change this approach and have a specific content for each version. For example the stuff added in this PR is only valid on versions 2.13+ and also in the current apporach we can't get links to the specific topics in the guide.

I think we should fix how the troubleshooting widgets are added to be per version, but do think they should all be in separate files as we have it today

Out of curiosity, why? The rest of the website is done this way :) I don't mind whether the items are in the same file or not, I just want to have it versioned and be able to give a link to specific problem.

To not be completely off topic, @yuvalweber could you please put your stuff the old way, as @tomkerkhove suggested and we will tackle the refactoring in a separate task. Thanks a lot!

[yuvalweber]

Added it in different section like you asked @zroubalik.
Let me know if anything else is needed

[yuvalweber]

Hey @tomkerkhove it won't let me merge because of your change request which I address to