User routes update

[kozabrada123]

TODOs

• Maybe add tests for Discord only routes / hard to test ones with the httptest crate, only to test we are sending everything correctly

Additions:

• get_user_by_username (note: Discord only)
• get_user_profile (#191)
• modify_user_profile (#192)
• disable_user (#193)
• initiate_email_change (#196 note: untested, SB has it differently)
• verify_email_change (#197 note: Discord only)
• get_pomelo_suggestions (#198 note: Discord only)
• get_pomelo_eligibility (#199 note: Discord only)
• create_pomelo_migration (#200 note: Discord only)
• get_recent_mentions (#201 note: Discord only)
• delete_recent_mention (#202 note: Discord only)
• get_harvest (#203 note: Discord only)
• create_harvest (#204 note: Discord only)
• get_user_notes (#205 note: Discord only)
• get_user_note (#206)
• set_user_note (#207)
• authorize_connection (#208 note: hard to test, the current testing server disallows all connection types)
• create_connection_callback (#209 note: hard to test)
• create_contact_sync_connection (#210 note: hard to test)
• get_connections (#211)
• get_connection_access_token (#212 note: hard to test)
• get_connection_subreddits (#213 note: hard to test)
• refresh_connection (#214 note: hard to test)
• modify_connection (#215 note: hard to test)
• delete_connection (#216 note: hard to test)
• get_user_affinities (#217)
• get_guild_affinities (#218)
• get_premium_usage (#220 note: Discord only)
• create_domain_connection (#547 note: Discord only)
• get_burst_credits (#219 note: Discord only)
• Add event RECENT_MENTION_DELETE
• Add event USER_CONNECTIONS_UPDATE
• Add event USER_NOTE_UPDATE
• Add type PremiumType for User premium type, instead of relying on u8
• Add type Harvest into types/entities/harvest.rs, along with related types
• Add type Connection into types/entities/connection.rs, along with related types

Changes:

• Break User::get into User::get (now for only other users) and User::get_current
• Change ChorusUser::delete to take an optional password
• Refactor a few routes to use chorus_request.deserialize_response() instead of panicing

[kozabrada123]

You may only link 10 issues

:(

[bitfl0wer]

@kozabrada123 Should I review this?

[kozabrada123]

@kozabrada123 Should I review this?

Sure, if you have the time