Add matrix strategy for CI + fix for Click 7.x.

[dwreeves]

Fixes #112, and lays groundwork for resolving #18.

Overview

I was working on resolving #18 when I noticed that the solution to this involves branching logic for Click 8 and Click 7.

I also noticed this library is getting more popular (congrats!) and people are starting to use it for more things.

In light of all this, I thought that before I address #18, I should significantly expand the scope of the CI so that all versions of Click that you say are supported, actually are supported.

Uncovering some regressions with Click 7.x support

In doing this, I discovered that the latest version of the code base in main actually has quite a few Click 7.x regressions.

In this code, I've fixed every regression I could see, except support for rich_config, which I could not get working.

Some of the regression fixes aren't the prettiest, but the fixes appear to work just fine.

Where to go from here

I feel like you can either keep as is, or you can add deprecation warnings for support to click 7.x and then remove that support in a future release.

[ewels]

This is massive, thanks for the work you've put into this!

I'm very happy to drop support for Click 7x. Click 8 has been around for a while now (since 2020) which I think is a fair period. And people can always install earlier versions of rich-click if that support was critical.

I'll merge now but if you fancy adding in some depreciation warnings within another PR that would be fab 👍🏻

[dwreeves]

I'll add some deprecation warnings, that sounds fine to me. So I have two PRs on my plate:

• Deprecation warnings for Click 7.x
• Fixing options inherited from context settings aren't applied #18.

Thank you for merging this!

[ewels]

Perfect, thank you!