Switch to getLiteUser where applicable on frontend

[nabramow]

This PR switches out useUser and useUsers with useLiteUser and useLiteUsers, which returns a much smaller user object. Backend code was already merged for this.

HOW TO TEST

• Check anywhere that it getLiteUser or getLiteUsers effects. This is anywhere you just have user avatar, name, etc (almost everywhere except profile and map). So references, chat, comments on communities and events, friend requests, host requests, etc.

Closes #4936

Web frontend checklist

• [ x ] Formatted my code with yarn format
• [ x ] There are no warnings from yarn lint --fix
• [ x ] There are no console warnings when running the app
• [ N/A ] Added any new components to storybook
• [ N/A ] Added tests where relevant
• [ x ] All tests pass
• [ x ] Clicked around my changes running locally and it works
• [ N/A ] Checked Desktop, Mobile and Tablet screen sizes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
couchers	✅ Ready (Inspect)	Visit Preview	Oct 26, 2024 6:16pm

[bakeiro]

wow such a nice job, looking good!

[bakeiro]

I'll test to see if everything works good on the page

[nabramow]

@aapeliv @bakeiro just checking up on this one. I did click around the app already for this but if anyone wants to take a second look I couldn't check the reference user info as I don't have any references in my test account (and can't add as I'm blocked by not having a profile photo and doesn't let me upload one on localdev).

Although we had pretty good tests for most of these components so hopefully it would catch anything.

[bakeiro]

sorry, totally forget, if the test was good then is a ready to go for me, I´ll check it briefly, if all good I approve it :)

[nabramow]

@bakeiro @aapeliv Okay whoops realizing I missed a big part of this by not using the GetLiteUsers new api so give me some time to adjust the hooks and re-write the tests!

[darrenvong]

This is exciting to see - the original useUsers hook implementation has been a hack all along to work around the limitation of not being able to get multiple users in one trip! I'd go as far to say a good measure of this new API doing its work is that there should be no useEffects and the weird workaround with the ref to store the list of user IDs once you've fully switched over to the new RPC!

[nabramow]

This is exciting to see - the original useUsers hook implementation has been a hack all along to work around the limitation of not being able to get multiple users in one trip! I'd go as far to say a good measure of this new API doing its work is that there should be no useEffects and the weird workaround with the ref to store the list of user IDs once you've fully switched over to the new RPC!

Thanks for this, I was getting hung up on refactoring the existing hook but this made me realize I should just re-write and use my own common sense haha, since the whole api call works differently.

Done now, re-wrote the tests. Could be missing some test cases, but I have most of the old ones covered (except the invalidate param since we don't need to pass that anymore).