[TASK-1096] Implementation of queries for organization

[pauloamorimbr]

Checklist

1. If you've added code that should be tested, add tests
2. If you've changed APIs, update (or create!) the documentation
3. Ensure the tests pass
4. Run ./python-format.sh to make sure that your code lints and that you've followed our coding style
5. Write a title and, if necessary, a description of your work suitable for publishing in our release notes
6. Mention any related issues in this repository (as #ISSUE) and in other repositories (as kobotoolbox/other#ISSUE)
7. Open an issue in the docs if there are UI/UX changes
8. Create a testing plan for the reviewer and add it to the Testing section

Description

This PR implements reactQuery hooks to be used on organization development.

Notes

The useOrganizationQuery hook was modified:

• A separated function was created to process organization data before returning it
• If the mmosEnabled feature flag is is true we created a mocked response, so we have better control on frontend development. This mock can be updated by the developer to create proper testing situations
• A enabled property was added to the query, to make sure it can only run after the sessionStore is loaded, since we need the currentAccount.organization.url to load the organization details in the new implementation, and it should not affect the current implementation.

Testing

Check for the mock data:

useOrganizationQuery is currently being used in accountSidebar, so one way of testing this implementation is to use:

  const orgQuery = useOrganizationQuery();
  console.log(orgQuery.data);

This way one can see the result of the data mocking with and without the mmosEnabled feature flag.

Check for the conditional query

On can comment out or add a setTimeout in session.tsx to prevent the sessionStorage.isPending from being set to false, causing the organization query to not run, waiting for it.

Other than code-related tests, there should be no changes in the current functionality.

[notion-workspace]

API handling and context changes for org mutations and fetches

[Akuukis]

• As funny as they are, I'm ok with naming because they are consistent and descriptive.
• blocked by refactor(account): query-ify OrganizationContext TASK-1194 #5164
• blocked by decision in internal chat

[duvld]

Just some questions

[duvld]

Should these be optional until the backend will actually return it? Or just returning false in the query is safe enough

[pauloamorimbr]

As far as I know, and from my tests, backend is already returning these fields. I'm setting it to false in the current query because when talking to @jamesrkiger we thought it would be a good idea to force the default "false" values until we have the front end properly implemented to avoid issues.

[duvld]

Look good to me now :)