Update routes to a RESTful Naming convention
As discussed in #49 (closed), the current route naming design is not scalable as the application will be bigger.
Before making an official release of this API, a major change will be to update the routes to a proper RESTful convention.
Also, this is an opportunity to version the API routes by adding a /v1 prefix to every route.
Perhaps, this change implies that everything that is integrated with the API will need to be updated (GUI, tests, etc), but the change is way more worth it than the extra work. And, it will be less impactful to do it now than later.