refactor(web): use queries for dealing with questions

[dgdavid]

In the context of #1439, replace Questions client by its equivalent using TanStack Query.

Additionally, it includes two commits with changes out of the scope of the PBI we're working on. Namely:

• Migrates the components/questions files to TypeScript, 560f953
• Stop re-exporting everything in components/questions/index.ts, 7c7b049

Tested manually with a LuksActivationQuestion

---

Related to https://trello.com/c/8u1WOJz4 (internal link)

[dgdavid]

We've agreed on not exporting all components in index file ( see https://trello.com/c/c0GEUMQ8 (internal link) and #1049). And this is a little step towards such an agreement. However, looking at it, two questions comes to my mind:

• Should we use ~/components/<namespace>/<Component> or ./<Component>. I see the first approach kind of safe and stable, since it does not matter from where you are importing the component.

• If we use ``~/components//does make sense to keep exporting _public_ components in the index file. For example, for importingQuestions.tsx` we could

  import Questions from "~/components/questions/Questions";

  or

   import { Questions } from "~/components/questions";

Honestly, for namespaces exporting a single component there is not too much difference / advantages. Another story is when importing multiple components from a single namespace, like core. Similar to what happens when importing components from PatternFly: it would be really annoying if we have had to import each component from its path.

Just sharing thoughts. No strong opinion here (yet 😝)

[dgdavid]

This three import also reminds me the article I shared on slack channel two weeks ago about naming: https://kyleshevlin.com/prefer-noun-adjective-naming

It isn't exactly the same case than the article, but maybe going for QuestionGeneric, QuestionWithPassword, and QuestionLuksActivation would make them more consistent from a naming POV. Again, no strong opinion.

[dgdavid]

Or maybe we could just drop the Question prefix/suffix since they are already in the questions namespace.

[coveralls]

coverage: 70.959%. remained the same
when pulling c8779b7 on use-query-questions
into 9fe32ae on master.

[imobachgs]

It looks almost good. Thanks!