Field name alias for APIs

[dasunhegoda]

• Identify the fields to develop aliases and update the ticket to match the API documentation.

WHAT WE HAVE:

API Path is the model to keep the information to use to request / return response from API modules. Since the need of field name alias is there.

WHAT WE NEED TO DO:

• [ ] From each field in the API, we need to add a button to create alias field name [new model] for that specific API Path only.
• [ ] Each alias field name can be accessible via the button box in API Path. [for reviewing & changing if needed]
• [ ] All the return response & docs route should be changed accordingly as well.
• [ ] API Path will need a new action for accessing its full form [new changes will be seen there]
• [ ] Fields need a better view than the many2may_tags to show the button on request [2].