standardize ellipsis usage (#10187)

in order to indicate "more content" or "content not relevant to example", we often use an ellipsis. in PHP and other languages, this pattern actually is relevant to the language.

this change standardizes usage of the ellipsis for the above examples to be in a comment. this give us valid PHP and Javascipt, and reduced ambiguity with the language construct.

Author: browner12

broadcasting.md

@@ -500,7 +500,7 @@ If you customize the broadcast name using the `broadcastAs` method, you should m
 
 ```javascript
 .listen('.server.created', function (e) {
-    ....
+    // ...
 });
 ```
 

passport.md

@@ -853,15 +853,15 @@ Then, attach the middleware to a route:
 
 ```php
 Route::get('/orders', function (Request $request) {
-    ...
+    // ...
 })->middleware('client');
 ```
 
 To restrict access to the route to specific scopes, you may provide a comma-delimited list of the required scopes when attaching the `client` middleware to the route:
 
 ```php
 Route::get('/orders', function (Request $request) {
-    ...
+    // ...
 })->middleware('client:check-status,your-scope');
 ```
 

queues.md

@@ -288,7 +288,7 @@ use Illuminate\Contracts\Queue\ShouldBeUnique;
 
 class UpdateSearchIndex implements ShouldQueue, ShouldBeUnique
 {
-    ...
+    // ...
 }
 ```
 
@@ -363,7 +363,7 @@ use Illuminate\Support\Facades\Cache;
 
 class UpdateSearchIndex implements ShouldQueue, ShouldBeUnique
 {
-    ...
+    // ...
 
     /**
      * Get the cache driver for the unique job lock.

reverb.md

@@ -176,7 +176,7 @@ use Laravel\Reverb\Pulse\Recorders\ReverbMessages;
         'sample_rate' => 1,
     ],
 
-    ...
+    // ...
 ],
 ```
 

telescope.md

@@ -276,7 +276,7 @@ Telescope "watchers" gather application data when a request or console command i
 'watchers' => [
     Watchers\CacheWatcher::class => true,
     Watchers\CommandWatcher::class => true,
-    ...
+    // ...
 ],
 ```
 
@@ -288,7 +288,7 @@ Some watchers also allow you to provide additional customization options:
         'enabled' => env('TELESCOPE_QUERY_WATCHER', true),
         'slow' => 100,
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -313,7 +313,7 @@ The command watcher records the arguments, options, exit code, and output whenev
         'enabled' => env('TELESCOPE_COMMAND_WATCHER', true),
         'ignore' => ['key:generate'],
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -343,7 +343,7 @@ The gate watcher records the data and result of [gate and policy](/docs/{{versio
         'enabled' => env('TELESCOPE_GATE_WATCHER', true),
         'ignore_abilities' => ['viewNova'],
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -391,7 +391,7 @@ The model watcher records model changes whenever an Eloquent [model event](/docs
         'enabled' => env('TELESCOPE_MODEL_WATCHER', true),
         'events' => ['eloquent.created*', 'eloquent.updated*'],
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -404,7 +404,7 @@ If you would like to record the number of models hydrated during a given request
         'events' => ['eloquent.created*', 'eloquent.updated*'],
         'hydrations' => true,
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -424,7 +424,7 @@ The query watcher records the raw SQL, bindings, and execution time for all quer
         'enabled' => env('TELESCOPE_QUERY_WATCHER', true),
         'slow' => 50,
     ],
-    ...
+    // ...
 ],
 ```
 
@@ -444,7 +444,7 @@ The request watcher records the request, headers, session, and response data ass
         'enabled' => env('TELESCOPE_REQUEST_WATCHER', true),
         'size_limit' => env('TELESCOPE_RESPONSE_SIZE_LIMIT', 64),
     ],
-    ...
+    // ...
 ],
 ```