docs: added a note to setting_status for guild cache

[Jaskowicz1]

This PR adds a note to setting_status.md about the guild cache, telling people how they can still display a guild count without the guild cache on (if they wish to do so). I'm not entirely sure if you can safely call the two methods I provided every 120 seconds without getting rate-limited, so if there's a better method then please do say!

Documentation change checklist

• My documentation changes follow the same style as the rest of the documentation and any examples follow the coding style guide.
• I tested that my change works before raising the PR (via running doxygen, and testing examples).
• I have not moved any existing pages or changed any existing URLs without strong justification as to why.
• I have not generated content using AI or a desktop utility such as grammarly.

[netlify]

✅ Deploy Preview for dpp-dev ready!

Name	Link
🔨 Latest commit	1a070ba
🔍 Latest deploy log	https://app.netlify.com/sites/dpp-dev/deploys/653240bf80dc3400088c2b69
😎 Deploy Preview	https://deploy-preview-955--dpp-dev.netlify.app/setting_status
📱 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.

[braindigitalis]

I wouldn't tell people to call get guilds. the result is huge, and doesn't work if the bot is on over 1000 guilds. it's also heavily rate limited.
application_get_current is the only practical option without cache.

getting application also works without any privileged intents