Endpoint JSON Schema's only registered if they match endpoint name

[marcvdijk]

Take the following endpoint decorator as example:

@endpoint('async_liemd_ligand', 'liemd_ligand_request', 'async_liemd_response',
options=RegisterOptions(invoke='roundrobin'))

I'm unable to call this endpoint resulting in the following error:

schema.exception.SchemaException: Schema name "async_liemd_ligand_request" with type
"endpoint", and version "1" on "mdgroup/lie_md" was not found

When I change the request endpoint name from 'liemd_ligand_request' to 'async_liemd_ligand_request' thus matching the endpoint name and making sure the associated JSON schema file is available the call to the endpoint works again.

I think is undesirable behaviour as:

• It seems that the second and perhaps even the third argument in the endpoint decorator have no
  use if they need to be the same as the endpoint name (first argument).
• It prevents JSON schema reuse in endpoints. In this case the request schema is equal to, and should
  be shared with, the non async version of the endpoint ('liemd_ligand')