BHoM_Adapter: refactoring- should all IBHoMObjects implement a default "base" comparer that when checking for equality first of all looks at the GUID?

Because I am not sure that the following is something we want (Push with RobotAdapter, which uses comparers):

here node duplicates are correctly filtered out -- but that just because they have a comparer implemented.

here bars duplicates are not filtered out -- even though they are have the same GUID (i.e. BHoM knows they are the same bar)

Implementing a default base comparer for IBHoMObjects that uses GUID for equality would solve this without having to manually implement a comparer for every type.
Not sure about potential side-effects though. `Replace()` and consequently Push, Pull etc should all work as usual, I think.

@IsakNaslundBh @al-fisher @epignatelli @adecler