Report binding problems to binding registry and show them as errors during test execution

[gasparnagy]

Some generic binding errors (e.g. [Binding] on a generic type) were not properly reported as errors so far, only as warnings, but those are usually not visible by test runners. Some of these errors were causing strange exceptions during execution, but it was hard to trace them back to the source problem.

Also type load exceptions blocked the discovery process that causes problems with tooling (e.g. VS) that uses the binding registry builder to discover the step definitions.

This PR introduces validity of loaded binding registry and provides a way to query these errors from the binding registry. During test execution, the invalid binding registry fails the tests by listing all collected error.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue).
• [ ] New feature (non-breaking change which adds functionality).
• [x] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Performance improvement
• [ ] Refactoring (so no functional change)
• [ ] Other (docs, build config, etc)

Checklist:

• [x] I've added tests for my code. (most of the time mandatory)
• [x] I have added an entry to the changelog. (mandatory)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

[gasparnagy]

@SabotageAndi the PR exposes a tuple on the IBindingRegistry interface (IEnumerable<(BindingErrorType ErrorType, string Message)> GetErrorMessages();) I don't know if this is a good practice, or whether we should create a new type for that. What do you think?

[SabotageAndi]

I would not put a tuple into a public interface. Feels wrong for me.

[gasparnagy]

@SabotageAndi OK, I agree. I will fix it

[gasparnagy]

@SabotageAndi pushed a new version without the tuple

[SabotageAndi]

@gasparnagy Ready to merge?

[gasparnagy]

@SabotageAndi yes, done.