[11.x] Added an event that reports files being deleted when calling the schema:dump --prune command

[andrey-helldar]

The art schema:dump console command is able to report the end of a job by sending the SchemaDumped event, but is unable to report file deletion if the command is called with the --prune parameter.

This PR adds a new event to implement this feature.

P.S.: I didn't find any tests to check both the art schema:dump command and the event, so I didn't add tests for the new event either.

P.S.2: The static analyzer error has nothing to do with my code :)

P.S.3: My case that started it all:

I am developing a package to export data from tables selected by the developer. Yesterday I added the ability to delete files, but I was surprised that in Laravel the SchemaDumped event doesn't contain a label when calling the console command with the --prune flag (and it shouldn't, because the essence of the event is related to the database schema, not to the files). That's why I decided to add a new event, called in case of launching a console command with the parameter of file trimming.

[taylorotwell]

I'm not sure if I would call the event SchemaPruned. The migrations are what is pruned.

[andrey-helldar]

@taylorotwell, I couldn't think of anything better at the time. I thought the name SchemaFilesDeleted was a bit too long, but still more appropriate. Or MigrationsPruned. What do you think?

[andrey-helldar]

I've started brainstorming for the best title. I'll be back with the final result.

[andrey-helldar]

@taylorotwell I can't say that many people participated in the brainstorm, but one of the suggested names is MigrationsPruned. I think it is more suitable for the name of the event and better reflects its essence.

There were also some less popular names:

• MigrationFilesPruned
• MigrationFilesDeleted
• MigrationsCleaned

I added a commit with the event name changed to MigrationsPruned.