Reactions state management with react query

[jnaviask]

Description

Follow-up for #4186. We should use react-query to store + mutate the state of reactions, rather than relying on raw HTTP requests + event emitters. See client/scripts/state/api/topics as a reference.

Engineering Requirements

• Logic for reactions encapsulated with react-query.
• New state folder for reactions that adds react-specific hooks.
• Use react-specific hooks for reactions rather than existing business logic.

Acceptance Criteria

No product-facing changes or regressions.

[CowMuon]

Looks like this is set to in progress but has no point estimate? @kurtisassad
Please see #4258 (literally the first item on the sub-task list.)

[mzparacha]

Did some work and apart from the reaction thread controller we have some API calls of reactions endpoints in the threads and some controllers. These are all the files that have some /reactions related API calls

• ThreadReactionsController.ts
• reactions.ts
• reactionCounts.ts
• threads.ts

what I am concerned about is threads.ts. Should we move the reaction-related API calls from threads.ts to the new react query /reactions state/folder for better organization

cc: @jnaviask @CowMuon

[jnaviask]

@mzparacha feel free to move the reactions functions around as needed -- if it makes sense to move them from threads.ts, then that's fine (see the old TODO anyway!).

[CowMuon]

This is under review and should be mergeable once @masvelio marks his comments as resolved.