Name collision on request/response objects

When two routes have the same name for a Request / Response the namespaces are clobbered. Example:

https://github.com/leeola/example_okapi_name_collision _([specifically this file](https://github.com/leeola/example_okapi_name_collision/blob/master/src/main.rs))_ will incorrectly report that the `/two` route has a response type of:

```
{
"reply": "string"
}
```

Instead of what it should be,

```
{
"different_schema": "string"
}
```

I'm happy to help developing a solution to this, but I'm unsure how best it can be handled. Ideally, I imagine something resembling idiomatic OpenAPI specs should be generated. Though, looking at the [classic PetStore example](https://petstore.swagger.io/) it looks like that entire bottom area is ripe for having many structure names occupy the same namespace.

Thoughts on how best to handle this?