Handle pending changes to tifffile defaults and avoid test warnings

[grlee77]

Description

closes #5337
closes #6558
closes #6572

I see no warnings from the IO module on my system, but it is possible some other versions of dependencies may still warn. Let's see how the tests here go.

We need to decide if we should be adding these kwargs in the plugins for backwards compatibility or if our policy is just to dispatch to whatever the tifffile defaults are when writing unless the user supplies kwargs. In this PR, I chose to automatically set the needed kwargs internally to the plugin for backwards compatiiblity and for consistent behavior across current and future tifffile versions.

For reviewers

• Check that the PR title is short, concise, and will make sense 1 year
  later.
• Check that new functions are imported in corresponding __init__.py.
• Check that new features, API changes, and deprecations are mentioned in
  doc/release/release_dev.rst.
• There is a bot to help automate backporting a PR to an older branch. For
  example, to backport to v0.19.x after merging, add the following in a PR
  comment: @meeseeksdev backport to v0.19.x
• To run benchmarks on a PR, add the run-benchmark label. To rerun, the label
  can be removed and then added again. The benchmark output can be checked in
  the "Actions" tab.

[mkcor]

Thanks for taking care of this! 🙏
I do see the warnings from the IO module on my system:

Python 3.9.4 | packaged by conda-forge | (default, May 10 2021, 22:13:33) 
scikit-image.git@29770dbc9fd34131d69b6f9c2fbb1ead835562cd#egg=scikit_image
tifffile==2022.5.4

[stefanv]

Looks good to me; just the one typo in the docstring, all the other suggestions are stylistic.