Feature debug

[chenkasirer]

Fixes #176

• Feature application now fails more gracefully. The last valid geometry is returned.
• Joint.add_features implementation raise BeamJoiningError when they fail to support joining of a pair of beams.
• Assembly component fills in a DebugInformation object with joining and feature errors.
• Two new components allow visually inspecting the different errors.

What type of change is this?

• Bug fix in a backwards-compatible manner.
• New feature in a backwards-compatible manner.
• Breaking change: bug fix or new feature that involve incompatible API changes.
• Other (e.g. doc update, configuration, etc)

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 added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• I ran all tests on my computer and it's all green (i.e. invoke test).
• I ran lint on my computer and there are no errors (i.e. invoke lint).
• I added new functions/classes and made them available on a second-level import, e.g. compas_timber.datastructures.Beam.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate)

[obucklin]

taking with fabio and jonas, we said we wanted to show the beams without features from the assembly component when there are no joint inputs or when CreateGeometry is False. I implemented this in my latest PR. I dont think it should cause any probelms.