[12.x] explain how to manually activate broadcasting routes (#10908)

* explain how to manually activate broadcasting routes

while the automatic attempts Laravel makes to activate broadcast routes cover a lot of cases, there are some it does not.  this change adds an explanation on how to manually activate routes if the Laravel magic fails.

* Update broadcasting.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>

Author: browner12

broadcasting.md

@@ -777,7 +777,15 @@ class ServerCreated implements ShouldBroadcast, ShouldDispatchAfterCommit
 
 Private channels require you to authorize that the currently authenticated user can actually listen on the channel. This is accomplished by making an HTTP request to your Laravel application with the channel name and allowing your application to determine if the user can listen on that channel. When using [Laravel Echo](#client-side-installation), the HTTP request to authorize subscriptions to private channels will be made automatically.
 
-When broadcasting is enabled, Laravel automatically registers the `/broadcasting/auth` route to handle authorization requests. The `/broadcasting/auth` route is automatically placed within the `web` middleware group.
+When broadcasting is installed Laravel attempts to automatically register the `/broadcasting/auth` route to handle authorization requests. If Laravel fails to automatically register these routes, you may register them manually in your application's `/bootstrap/app.php` file:
+
+```php
+->withRouting(
+    web: __DIR__.'/../routes/web.php',
+    channels: __DIR__.'/../routes/channels.php',
+    health: '/up',
+)
+```
 
 <a name="defining-authorization-callbacks"></a>
 ### Defining Authorization Callbacks