State management

[cdrice26]

I've added the state management and custom useState hook to the software, and also pulled in the real meals into the AvailableMeals table. The custom meal editor and sorting logic are not yet implemented, they will be a separate PR.

[nickslick03]

This looks awesome! 2 things:

• on line 34 of app.tsx, the second parameter for the usePersistantState for the mealQueue is this: new Array<Meal>().fill({} as Meal). I tried replacing it with an empty array and nothing went wrong. Is all that intentional?
• in the mealQueue, the the addMeal function clears the mealQueue but doesn't clear the days selected. I think it should be the other way around, in the case a user wants to keep some meals for different days but is more likely to choose completely different days. There's also a "clear meal queue" button for that case. One could argue that removing all the meals from the queue is a confirmation to the user that the meals have been added, so I think creating a notification component that transitions in from the top whenever a notable state-changing button is clicked would help. I can assign that task to myself if you think it's necessary.

[nickslick03]

I also just added some memos in the mealQueue to disable the add button if no meals are in the queue or no days are selected and disables the clear button if there's no meals in the queue.

[cdrice26]

I've implemented the changes you requested, I agree, those make sense. Yes I think a notification component is a good idea.