Feat/40 implement individual food item screens

[frostymate]

These changes collectively enhance the user experience by providing detailed views of individual food items and ensuring robust test coverage for new features.This pull request introduces a new feature allowing users to view details of individual food items within the ShelfLife app. The changes include updates to navigation, view models, and UI components to support this feature. I have added nice UI Screen. However, there are things to be worked on as I need to add testing which will be done in [#91], additionally there are some values like font sizes that are hardcoded that I will eventually do. Finally, I believe that the database has to be structured in a way that food items should be collections and each food item should have sub-collections containing their instances. This would make retrieval of instances of the same Food Item very efficient however this is quite an ambitious task that I will leave for M3.

Navigation and Routing Enhancements:

• Added IndividualFoodItemScreen to the list of composable screens in MainActivity.kt and defined a new route for it. [1] [2]
• Introduced a new constant INDIVIDUAL_FOOD_ITEM in NavigationActions.kt and a navigation method navigateToIndividualFood. [1] [2]

ViewModel Updates:

• Added searchedFoodItems state flow and methods setSelectedFoodItem and its corresponding getter to HouseholdViewModel.kt to manage and retrieved the clicked food item. [1] [2]

UI Component Modifications:

• Modified FoodDisplayComponents.kt to make food items clickable and pass a click handler to FoodItemCard. [1] [2] [3] [4]
• Updated Overview.kt to handle food item clicks and navigate to the individual food item screen.

New UI Screen:

• Created IndividualFoodItemScreen to display detailed information about a selected food item, including its name, image, and nutritional facts.

New Utility Component:

• Added FoodItemDetails.kt to encapsulate the display logic for food item details.

Test Coverage:

• Added comprehensive tests for IndividualFoodItemScreen to verify correct display and navigation behavior.
• Introduced FoodItemDetailsTest to ensure the FoodItemDetails component displays food item details correctly.

Code Refactoring:

• Made ListFoodItemsViewModel and HouseholdViewModel open classes to allow for easier testing and extension. [1] [2]
• Minor cleanup in build.gradle.kts and other files for consistency and readability. [1] [2]

[frostymate]

Some difficulties were encountered as my first attempt of passing the selectedFoodItem as a parameter was quite complicated to test and was very complex. So instead I am using the viewModel in order to interact and store the selectedFoodItem.

[frostymate]

The Coverage of New Code is under 80 but for the main files modified/added they have a high coverage. The other files will have their coverage increased before M2.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
71.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud