feat(collectors): add command and scheduled tasks collectors

[countless-integers]

Adds collectors for cli commands and scheduled tasks.

Closes #75

todo:

• tests ¹
• extra metadata (especially for scheduled tasks) (?)

1: not sure what to do with tests for the scheduler the classes are missing in L5.5 + some issues with starting test in command collector

[countless-integers]

It gets interesting when a command fails though. I'm missing some way to report the error :/ . Perhaps some global exception listener in the framework collector (if it's not there already and I'm just no seeing it, I have a vague recollection that I've seen errors reported before...)

[arkaitzgarro]

It gets interesting when a command fails though. I'm missing some way to report the error :/ . Perhaps some global exception listener in the framework collector (if it's not there already and I'm just no seeing it, I have a vague recollection that I've seen errors reported before...)

CommandFinished event includes a $exitCode property. Can it be that the event is fired for both successful and failed commands? https://github.com/laravel/framework/blob/43bea00fd27c76c01fd009e46725a54885f4d2a5/src/Illuminate/Console/Application.php#L93

[countless-integers]

It gets interesting when a command fails though. I'm missing some way to report the error :/ . Perhaps some global exception listener in the framework collector (if it's not there already and I'm just no seeing it, I have a vague recollection that I've seen errors reported before...)

CommandFinished event includes a $exitCode property. Can it be that the event is fired for both successful and failed commands? https://github.com/laravel/framework/blob/43bea00fd27c76c01fd009e46725a54885f4d2a5/src/Illuminate/Console/Application.php#L93

I'd expect that. I'll see if I can reproduce it and adjust the "fake status code" from 200 to something else. If I remember correctly, in Symfony, the command could return a status code in the handle method and that was it.

However what I meant was when an exception is thrown and not handled in the command, then listener doesn't seem to fire, but the app terminate middleware executes send on the agent. In phikra there was this naughty thing that adding errors.

[countless-integers]

Ok, I've added the status code check.

I've also noticed I've been wrong about CommandFinished -- it doesn't seem to fire when there's an unhandled exception thrown in the command. Terminate middleware still sends data to APM though.