Enable writing to JSON without including BHoM-specific attributes

[tg359]

Description:

When handling JSON files unrelated to BHoM (such as config files for external programs), it would be nice to be able to handle these files and re-save them without including any BHoM attributes (guids, etc) that we get when serialising from a customObject to a JSON file.

[alelom]

Sorry, I realized this can't work - we need to change how the UI behaves when it sees a deserialized object that is unknown (not bhom).
That's why we are now "wrapping" in a CustomObject, so that then the Explode can explode it. The annoying part is that the CustomObject is a BHoMObject, instead of an IObject, and this is driven by the fact that we are storing the properties in the CustomData dictionary. It means we need to go and change base bhom serializer and ui, can't be done from the File_Toolkit directly.