Improve handling of non-string values for 'override_tag's 'default_html' argument

[alxbridge]

Description

Fixes #211

Raises a (more) meaningful TypeError if a call is made to override_tag with something other than a string as the default_html arg. This raised error provides some context for the bad call, which was not provided in the traceback when thrown directly by Django >= 4.0.

If run in Django < 4.0, this PR causes a warning to be logged instead, giving developers on those older versions advance warning of the change.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have added an appropriate CHANGELOG entry

[zerolab]

fwiw, I tested the fix the warning suggests on an active project and that fixed the PL issue

[alxbridge]

NB I've pushed an updated version of this PR with an extra commit to allow the tox config to run. However, it looks like there are other PRs to address this same issue in other ways: if preferable I can remove this again, now I can see all checks have passed.

[bcdickinson]

I like this approach, but I don't think the provided type annotations are correct. It would also be great to see some tests that check the new exception behaviour.

[alxbridge]

@bcdickinson I believe I've addressed the changes you requested - please could you re-review?

[olivierphi]

I don't have a deep knowledge of the internals of this package, so my review is rather superficial...
That said, I have 2 small comments - that you're of course free to ignore as on this codebase I've never touched before you likely know much better than me what you're doing, 😄

[olivierphi]

Happy to approve that PR 🙂 🎈

Addressed in subsequent commit