API routes and documentation

[Garlikdev]

Routes

• Think about more descriptive api routes.
• /usermgnt route works only for tmnf, tm20 and discord data, needs password and email change too or make it a 3 separate routes e.g. /user/password, /user/trackmania, /user/email. Don't force me to work with all-in-one optional values form. That's a pain in the butt to type and validate correctly.
• /records/* returns string instead of json type.
• /spreadsheet, /wrleaderboard, /records etc. data should be aggregated in the backend and return clean data without filtering in frontend. @.garlik me on discord so we can come up with the queries
• /performance/* response is different than in docs. It should be array of objects
  {
  "edition": 1,
  "fins": 70
  }

Docs

• /manage/maps error returns string or object, so make it either or