TMS-service: Rationalise the API endpoints

[Justus-at-Tazama]

The current API endpoints for the respective ISO20022 messages are:

pain.001 - execute
pain.013 - quoteReply
pacs.008 - transfer
pacs.002 - transfer-response

Note: Discussion required before starting

Acceptance criteria:

1. Create v1 of the TMS API
2. Rationalise the names to be less Mojaloop and more ISO20022
3. Standardise the names to have some sort of consistent pattern (i.e. use the anticipated TxTp value as the name of the endpoint)
4. Remove the validation of the TxTp object from the API endpoint
5. Add the TxTp object (key and value) to the incoming message based on the end-point where the message is received.
6. Update documentation
7. Update swagger doc
8. Decommission previous end points

[Sandy-at-Tazama]

Please rename as follows