Phasing out Honeybadger

[ChrisZenhub]

having honeybadger complicates many things, such as

• setting up project on for new contributors (tedious preparations such as installing proper ironpython, anaconda, ...)
• installation (getting files from all places)
• compatibility (e.g., I have rhino 7 and 6 installed now and rhino 7 won't open the honeybadger components. on a clean install rhino 7 only, it worked)
• code maintenance

The original added value of honeybadger (beginner programmers being able to write little scripts for Hive in python) turned out to be not very important, since Hive reached a complexity where we can't effectively work with very-beginner programmers?

This epic needs to be broken down into several issues for individual honeybadger components and an issue for a general architecture design of the visual studio project to accomodate the honeybadger projects sensibly

Process

We will only migrate the following modules since the others seem to be redundant:

• epw-reader
• sia380
• solar

We will keep Hive.Core as but remove it from build to create a purely .NET solution. If migration shows we dont need those seemingly redundant components, then eventually remove Hive.Core

[ChrisZenhub]

wohoo Epic is done @mmatache25 @philipschulz !

one little new issue #732, but we can put it to the Bugs epic