Fix generated schema name conflicts

[DmitrySboychakov]

this PR fixes two issues within swagger
in our project we have multiple member enums with the same name, for example:

class SomeObject{
    public enum Type {
        TypeValue1,
        TypeValue2;
    }
}

the commit TypeNameResolver to handle member class names correctly fixes the override for that enums and classes to generate SomeObjectType instead of Type

The second commit fixes overall schema name conflicts if there different classes with the same name exists in different packages by appending numeric postfix to the schema name