BUG: fix for matplotlib 3.5 + symlog + linthresh value outside data range

[neutrinoceros]

PR Summary

fix #3564

Here's the results from #3564's script with this branch with matplotlib 3.4 or 3.5

So we even gained minor ticks for matplotlib 3.4, which alleviate most of the problem I reported in #3537 🎉
opening as a draft for now, will open for review if CI stays green

[neutrinoceros]

switching to draft while we're stabilising the auto backport system

[cphyc]

Note: the warning will be slightly erroneous if both zmin and zmax are negative. Maybe change it for something like

Suggested change

	f"the data range ({zmin}, {zmax}). Switching to log norm."
	f"the absolute data range ({abs(zmin)}, {abs(zmax)}). Switching to log norm."

[neutrinoceros]

Ah, you have a point, but your suggestion has a drawback too when values are both negatives because their absolute values are now in reversed order. I'll try to improve over it.

[neutrinoceros]

better now ? (sorry, I forced pushed again, but only the warning message was changed)

[cphyc]

Yup, I clicked the auto-merge button ;)

[neutrinoceros]

thank you !

[neutrinoceros]

@meeseeksdev backport to yt-4.0.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout yt-4.0.x
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 ecf9a8253b3386b0a9d87e9f99c85ec337d3fbfa

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #3565: BUG: fix for matplotlib 3.5 + symlog + linthresh value outside data range'

4. Push to a named branch :

git push YOURFORK yt-4.0.x:auto-backport-of-pr-3565-on-yt-4.0.x

5. Create a PR against branch yt-4.0.x, I would have named this PR:

"Backport PR #3565 on branch yt-4.0.x (BUG: fix for matplotlib 3.5 + symlog + linthresh value outside data range)"

And apply the correct labels and milestones.

Congratulation you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove Still Needs Manual Backport label once the PR gets merged.

If these instruction are inaccurate, feel free to suggest an improvement.