Handle HashSet, FragmentSet,... as input list

[adecler]

NOTE: Depends on

BHoM/BHoM#853
BHoM/BHoM_Adapter#228
BHoM/BHoM_Engine#1743

(at least for testing)

Issues addressed by this PR

Closes #154

IEnumerable types are can now be properly inputted as lists:

Test files

Use any CreateObject component as add inputs for Tags and Fragments.

Changelog

Additional comments

I had to do a second commit to fix a problem created from a previous PR: Added inputs to a CreateObject component would not work properly after copy paste or reopening the file.

[pawelbaran]

LGTM, tested on autoconstructors of objects with HashSet properties, works fine.

[IsakNaslundBh]

Tested, and works fine as long as everything is plugged in, but found some cases that crashes out:

1. Adding a fragments input and leaving it unplugged makes the component go red and give a "1. Solution exception:Object reference not set to an instance of an object." error. I know you can just remove the input and that it only happens if a user explicitly has added it, but think it would be good for this to just work.

2. Adding two of the same fragment type crashes with the same "1. Solution exception:Object reference not set to an instance of an object." error. This arguably should be crashing, but an error like "Can only add one fragment of a particular type to a BHoMObject" or similar instead of a null reference exception would be better I think:

Apart from that, things seem to be working well. Also love that fragments now work in the explode! 👍

[adecler]

Thanks @IsakNaslundBh ,

• The issue of the default input turning the component red is actually a Grasshopper problem created by the changes here. I have fixed it in Take care of input type that are both list and items Grasshopper_UI#505
• The second problem you raised was caused by something that have been annoying me for a while now so I am glad to have an opportunity to fix it 😄. (see new commit)
  

Can you do a final review and approve all five PRs if you're happy with it ?

[IsakNaslundBh]

Issues I had got solved with the latest commit(s), and have not found any problems when using the UI!

[adecler]

/azp run BHoM_UI.CheckInstaller

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).