Resolve deprecation warnings

[freak4pc]

Hey there! :)
The project has Matcher deprecations for a while, but many methods and classes using Matcher aren't market as deprecated. This causes manny inner warnings inside Nimble itself.

For consumers using SPM there's no real way to turn this off.

I've marked all consumers of Matcher as deprecated themselves to resolve this.

[ikesyo]

Thanks for tackling this! Those deprecation are planned as stated in the README. But some of them seem not correct to me.

[freak4pc]

Thanks @ikesyo - I'm a bit confused on how it could be possible (theoretically / puristically speaking) to deprecate a type that has non-deprecated methods counting on it?

If there is a method X that counts on type Y and the former isn't deprecated, it makes sense the latter isn't as well. So, does this really make sense having Matcher completely deprecated in this sense?

[mthormann-dhi]

Any update on this?

[ikesyo]

Superseded by #746.

[freak4pc]

Always fun having a different PR supersede yours that wasn't reviewed for almost a year... Oh well :)