[experimental] Add listing tip to Middlewares documentation (#2852) (#2860)

* docs(backend): correct TypeScript code fences in TS tabs (controllers, services, middlewares, routes)

* docs(bundlers): clarify webpack config example rename and JS/TS filenames

* docs(routes): add guidance to prefer fully-qualified handler names in custom routers

* docs(api-tokens): add concise security tip (least privilege, rotation, secrets manager)

* docs(controllers): add caution about validateQuery/sanitizeQuery/sanitizeOutput when overriding actions

* docs(policies): clarify scoped policy folders and fix example path

* docs(webhooks): add signature verification tip and fix TS config path

* docs(theme-extension): add minimal TS example for theme.light and theme.dark overrides

* docs(wysiwyg): add next steps tip (plugin first, custom field for deeper integration)

* docs(middlewares): add tip to list registered middlewares (discovery command)

* Limit PR scope based on title; keep only intended doc(s); revert unrelated files

* Revert accidental fence change to ts; keep only the tip (PR #2852)

---------

Co-authored-by: GitHub Actions <[email protected]>

Author: pwizla

docusaurus/docs/cms/backend-customization/middlewares.md

@@ -129,6 +129,10 @@ export default () => {
 
 The GraphQL plugin also allows [implementing custom middlewares](/cms/plugins/graphql#middlewares), with a different syntax.
 
+:::tip Discover loaded middlewares
+Run `yarn strapi middlewares:list` to list all registered middlewares and double‑check naming when wiring them in routers.
+:::
+
 ## Usage
 
 Middlewares are called different ways depending on their scope: