Recommend fully qualified handler names in Routes documentation (#2845)

* 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

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

---------

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

Author: 2 people

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

@@ -168,7 +168,7 @@ export default factories.createCoreRouter('api::restaurant.restaurant', {
 </TabItem>
 </Tabs>
 
-This only allows a `GET` request on the `/restaurants` path from the core `find` [controller](/cms/backend-customization/controllers) without authentication.
+This only allows a `GET` request on the `/restaurants` path from the core `find` [controller](/cms/backend-customization/controllers) without authentication. When you reference custom controller actions in custom routers, prefer the fully‑qualified `api::<api-name>.<controllerName>.<actionName>` form for clarity (e.g., `api::restaurant.restaurant.review`).
 
 ### Creating custom routers