[Feature] Laravel Livewire 3 Support

[mikebronner]

Describe the feature you'd like

Would love to see Livewire traces being supported.

Is your feature request related to a problem?

Currently unable to effectively filter livewire requests, all livewire messages, regardless of resource, are grouped under a single resource name. Each livewire message should be considered its own route, as opposed to a sub route of the livewire message.

Additionally, it would be extremely helpful to be able to inspect the request payload.

Describe alternatives you've considered

Alternative would be complex custom meta data tagging, which might bloat all my traces unnecessarily, and we would have to figure out how to hook into Livewire's events in the request stack.

Additional context

No response