[Challenges / Rules] Add back CAPTCHA_BOX

[patriciasantaana]

Summary

Adds back default ::CAPTCHA_BOX:: token to Rules error tokens

Documentation checklist

• The documentation style guide has been adhered to.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/rules/	@pedrosousa, @cloudflare/pcx-technical-writing

[patriciasantaana]

@migueldemoura can you take a look?

[github-actions]

Preview URL: https://143fa288.preview.developers.cloudflare.com
Preview Branch URL: https://patricia-pcx18773-captcha-box.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/rules/custom-errors/reference/error-tokens/	https://patricia-pcx18773-captcha-box.preview.developers.cloudflare.com/rules/custom-errors/reference/error-tokens/

[stepbrobd]

On the user side (my enterprise zone is sponsored by Cloudflare Project Alexandria so I'm happy to help out 🫡), ::CF_WIDGET_BOX:: is basically a catch all. I'm using it for non-interactive error pages (500 class errors, 1000 class errors, and Rate limiting block), and interactive error pages (IP/Country challenge, Managed challenge / I'm Under Attack Mode)

Even though in #23258 (comment), the error indicates that ::CAPTCHA_BOX:: is required, I was still able to successfully set the custom error page with only ::CF_WIDGET_BOX:: in the template

My speculation here is that ::CAPTCHA_BOX:: was indeed deprecated in the backend, but the error message returned was not changed along with the deprecation

[patriciasantaana]

On the user side (my enterprise zone is sponsored by Cloudflare Project Alexandria so I'm happy to help out 🫡), ::CF_WIDGET_BOX:: is basically a catch all. I'm using it for non-interactive error pages (500 class errors, 1000 class errors, and Rate limiting block), and interactive error pages (IP/Country challenge, Managed challenge / I'm Under Attack Mode)

Even though in #23258 (comment), the error indicates that ::CAPTCHA_BOX:: is required, I was still able to successfully set the custom error page with only ::CF_WIDGET_BOX:: in the template

My speculation here is that ::CAPTCHA_BOX:: was indeed deprecated in the backend, but the error message returned was not changed along with the deprecation

@stepbrobd thank you for letting us know! Let me flag this over to the team to get it fixed on the Cloudflare dashboard 🙂