Provide laravel 11 compatibiity

[Naoray]

Description

Upgrade to support Laravel v11.

All changes affecting developer using this packages have been documented in https://github.com/mollie/laravel-mollie/blob/provide-laravel-11-compatibiity/UPGRADE.md.

tl;dr;

• dropped lumen support
• directly inject MollieApiClient with ApiKey into Container to avoid having a wrapper class which needs to be updated everytime we add more functionality to underlying mollie api php sdk
• removed a bunch of code that was only accessed in testing or not used at all from MollieConnectProvider
• removed a bunch of tests that were only testing underlying libraries (Socialite and Mollie Api PHP tests already cover these cases)
• removed MollieManager and also the need to call ::api() on every endpoint call

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation only (no code changes)

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Todos:

• [x] check if licesce should change to MIT
• [x] check what other link to provide in readme instead of https://www.mollie.com/nl/blog/post/werken-bij-mollie-als-developer/
• [x] check if webhook support should be implemented
• [x] change image on readme to reflect code changes
• [x] check if telephone number at bottom of readme is still correct?! (+31 20-612 88 55) -> maybe remove it
• [ ] contact mollie to allow updated github actions (s. https://github.com/mollie/laravel-mollie/actions/runs/8187985704)

[sandervanhooft]

Thanks @Naoray ! It would be really helpful to list all proposed breaking changes and review/discuss these as part of this PR. Either as a separate upgrade guide document or in the comments here. Especially the Wrapper has received much work that's worth taking a second look at.

[jnoordsij]

Although I must say I'm very much a fan of most of the proposed changes, I do wonder if they should be tied to a major Laravel release. Especially with it being scheduled to release tomorrow and finishing the work on this MR + review process most probably taking a bit longer than that, might it not be more opportunistic to add Laravel 11 support individually (which I think is possible without needing any BC changes looking at #236) and handle the proposed further changes here afterwards?

That also makes it a lot for easy for people looking to upgrade to Laravel 11, given that they can do so without requiring them to also immediately update to the new version of this package all of a sudden.

[sandervanhooft]

Thanks @jnoordsij

We weighed our options and are going with a new major release