Metrics validate that the matcher is supported

[msschwartz21]

Closes #83

Ultimately we are embracing a very manual/hard-coded approach. Each metric has to implement its own _validate_matcher function that can check both the name of the matcher and any associated parameters that may be relevant for that metric. For example, IOUMatcher is only valid for division metrics if one_to_one=True.

Types of Changes

What types of changes does your code introduce? Delete those that do not apply.

• New feature or enhancement

Which topics does your change affect? Delete those that do not apply.

• Matchers
• Metrics

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the developer/contributing docs.
• I have added tests that prove that my feature works in various situations or tests the bugfix (if appropriate).
• I have checked that I maintained or improved code coverage.
• I have checked the benchmarking action to verify that my changes did not adversely affect performance.
• I have written docstrings and checked that they render correctly in the Read The Docs build (created after the PR is opened).
• I have updated the general documentation including Metric descriptions and example notebooks if necessary.

[cmalinmayor]

Generally looks good! Thanks for implementing :) just left a few comments inline

[cmalinmayor]

Could just return name in valid_matchers but this is a style thing

[cmalinmayor]

Approving with the caveat that it should be strictly greater than 0.5 for true one-to-one-ness :) but I don't feel the need to review again once that's fixed!