Handle duplicate namespace (struct) names

[jessepeterson]

Some commands like DeviceInformation and Settings have duplicate defined structures in the schema (e.g. OrganizationInfo. These can clash and cause compile failures.

An earlier version of the code generator prefixed all structures with a shortened version of the command name. For example "DI" would prefix all "DeviceInformation" structures. So this would be DIOrganizationInfo and SOrganizationInfo. You could prefix the whole command name, of course, but then we start getting really long names.

[jessepeterson]

We could try to deduplicate the structures ourselves but this has problems when we're only processing a single (or subset) of commands that do not take into consideration the files not being processed. Also the de-duplication effort would need to compare structures to see if they're actually, truly, different. A custom deep compare. Which sounds annoying.

[kilpatds]

I was thinking "Oh, I'm sure they're really the same structure"

Uh, they're not.

settings/OrganizationInfo : a dictionary of Organization{Name,ShortName,Address,Phone,Email,Magic} strings.
infomation/OrganizationInfo: a string (key to the other one. I think is supposed to match with "Magic" ??)

[jessepeterson]

Looks like settings.yaml and application.extensions.listactive.yaml generate duplicate structs with some other thing that I haven't looked into.