[1.x] Make migrations publishable

[toitzi]

Similiar to other first pary packages i thought it would be great to allow publishing migrations. Same as in this pr #80: a more practical use case might be if you use something like tenancy for laravel where you might want to have those migrations for your tenant databases as well

[SRWieZ]

This will also be useful for skipping the migration in test

Example, by wrapping the up() function with

if (app()->runningUnitTests()) 

[timacdonald]

@SRWieZ If you want to disable Pulse during tests, you should set the env - otherwise it'll be doing work during the test still - but just swallowing exceptions.

<server name="PULSE_ENABLED" value="false"/>

[timacdonald]

Publishing migrations is also nice as it gives the apps control over the indexes, which may be optimized further for specific applications.

[taylorotwell]

@timacdonald @jessarcher we are moving most of our first party packages to only publishing migrations (never running them behind the scenes). We are making this change for Sanctum and maybe others in Laravel 11.

It may be good to go ahead and just take this approach here?

[timacdonald]

@taylorotwell dig it. Updated this one and updated the docs over here: laravel/docs#9176

[taylorotwell]

Conflicts. 😅

[jbrooksuk]

@taylorotwell I've resolved the conflicts.