Fix Model Conversion

[Sefriol]

• Comments were overwriting EnumValues. I do not think this should be the case. Atleast it is not documented DTDL language specification
• Current generator assumes that every model starts with uppercase letters. This is not always the case. This change ensures that classes/modules are written and then referenced with uppercase letters.

[jarz]

@ms-mikeb: I can't recall the (historic?) reason for the SourceValue behavior with enum comments. Thoughts?

[Sefriol]

@jarz Any updates? I can iterate this if need be.

[ms-mikeb]

@ms-mikeb: I can't recall the (historic?) reason for the SourceValue behavior with enum comments. Thoughts?

Sorry for the late reply on this. We have an old system we needed to be able to map the value we're storing in the Comment field to an attribute that's added to the model in C#. I recognize this behavior wasn't documented well, nor is it intuitive. I'll need to see what alternatives we can look at for managing this so we can retire this behavior.

[ms-mikeb]

@jarz Any updates? I can iterate this if need be.

@Sefriol

I would say, let's make an issue to track the Comment, and just focus the PR on the casing support.

[Sefriol]

Changed the logic so that Comment takes precedence over enumvalue. There were some other issues with enum property names that I wanted to fix as well, so I kept those.