Make events key case insensitive

[paulhennell]

So mailgun appears to be insane and mixes their event names in upper and lowercase. 🤢

For example the event type "clicked" and "opened" are sent as "CLICKED" and "OPENED" while "delivered" and "failed" are just "delivered" and "failed".

This doesn't appear to be clear in mailgun docs or mentioned in the docs here, but the config file is case sensitive so you need the same case as the mailgun event to call the right job type:

        'delivered' => \App\Jobs\Mailgun\HandleDelivered::class,
        'CLICKED' => \App\Jobs\Mailgun\HandleClicks::class,
        'complained' => \App\Jobs\Mailgun\HandleComplaints::class,

Rather then this project trying to advise on what mailgun's current events are, and which case they should be referenced in, this PR sets a fallback event type to use a lowercase version of the event name.

So both the above config and the more natural setup below will work:

        'delivered' => \App\Jobs\Mailgun\HandleDelivered::class,
        'clicked' => \App\Jobs\Mailgun\HandleClicks::class,
        'complained' => \App\Jobs\Mailgun\HandleComplaints::class,

The fallback is a little ugly, but it should avoid breaking changes where people are using the uppercase, but allows others to use lowercase rather then go mad wondering why the one event doesn't work!

[paulhennell]

So fun fact: mailgun's test webhooks are in capitals. Presumably the real life ones are not, as OPEN, CLICKED etc only worked when changing the config file to use lowercase for real events. 😡

I guess this actually means the fallback isn't really needed - if you have capitals your hooks only work with the testing events, anything live would be in lowercase. So a cleaner config("mailgun-webhooks.jobs.{$jobConfigKey_lower} would be enough, and all configs would have to be in lowercase to work.

Going to go take this argument to mailgun now as what's the benefit of a test system that's different?

[cyrillkalita]

Addresses, if slightly differently: see 9.0 release notes