Laravel Octane Support: Scoped service binding

[coleshirley]

See #2010

@danharrin As I was working on this I found there is an issue with octane itself where scoped services aren't being flushed correctly because of a discrepancy between octane and laravel itself. laravel/octane#500

There is a workaround where after this pull request is submitted you can add the filament service to octane's flush services in the config like so:

config/octane.php:

<?php

...

return [

   ...

    /*
    |--------------------------------------------------------------------------
    | Warm / Flush Bindings
    |--------------------------------------------------------------------------
    |
    | The bindings listed below will either be pre-warmed when a worker boots
    | or they will be flushed before every new request. Flushing a binding
    | will force the container to resolve that binding again when asked.
    |
    */

    'warm' => [
        ...Octane::defaultServicesToWarm(),
    ],

    'flush' => [
        'filament'
    ],

  ...

];

Is that something that should be added to the documentation or do you want to just refer people here? Once the issue in the octane package is resolved we won't need to add that item to the flush in the config

[danharrin]

Hey, let's refer people here. I don't want to add documentation that we then have to remove later when Laravel fixes the issue.

Thanks for the PR!