fix(JsonSchema): avoid schema name collision when an operation name is already used by another class

[wuchen90]

Q	A
Branch?	4.2
License	MIT

When two API resources have the same class short name but are in different namespace, the schema section of OpenApi specs will only keep the first one.

Given

NamespaceA\MyResource:
  - propertyA: string

NamespaceB\MyResource:
  - propertyB: string

The current buggy behavior will produce a openapi.json like this with only one schema =>

{
  "components": {
    "schemas": {
      "MyResource": {
        "type": "object",
        "properties": {
          "propertyA": {
            "type": "string"
          }
        }
      }
    }
  }
}

So this leads to operations that use NamespaceB\MyResource will references to NamespaceA\MyResource schema.