feat(explore): implement base of the explore screen

[Zafouche]

Things that still need to be implemented:

• [ ] Interactions

  • [ ] Clicking on an association brings us to their association profile (with a back button available).
  • [ ] Typing in the search bar should display all accordingly filtered associations, in a simple column lazy list, where the items will show up in a small height but take the screen's width (just like common search suggestions in most applications that we use).
  • [ ] Bottom navigation bar needs to be added.

• [ ] Data queries (can be done later in a different PR)

  • [ ] The explore view model should be used, and use its list that gets the data directly form the firebase database.
  • [ ] A way to fetch their logo and display them instead of the gray box.

• [ ] Design (can be done later in a different PR)

  • [ ] Actual design that's more accurate to the figma when it is finalized. This includes positioning, fonts and colors.

[Zafouche]

This is what it looks like for now, none of the actual design is here since the figma needs to be further developed, only the logic is implemented.

Logic: Associations are sorted as such: vertically, they are separated by category, and then in each category, they are displayed and sorted alphabetically (regarding their acronym's first letter) horizontally

[Zafouche]

The duplicate code analysis is the mock list of associations, would probably be good to move it on the firebase database when we decide how and when a category of an association is chosen.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
78.0% Coverage on New Code (required ≥ 80%)
13.6% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[Zafouche]

Will have to remove the MockAssociations class later in a different PR to remove code duplicates.