fix: Use configured server time when calling RepositoryMeals.get_today() method

[michaelclark2]

What type of PR is this?

(REQUIRED)

• bug

What this PR does / why we need it:

(REQUIRED)

When a user calls the endpoint /api/households/mealplans/today , the api uses a hardcoded timezone of UTC to find todays date. This can lead to unexpected results when the user expects the configured timezone to be respected, as it is for the DAILY_SCHEDULE_TIME. To remedy this, I added a timezone argument to the get_today() method of the RepositoryMeals so that when we specifically want to use the configured server time we can, while omitting the flag to respect the UTC timestamps used in the database.

• added tz argument to get_today method signature with a default of UTC
• set tz to local tz when calling get_today method in the GroupMealplanController
• set tz to local tz when calling get_today method in create_timeline_events

Which issue(s) this PR fixes:

(REQUIRED)

Fixes: #4263

Testing

I manually tested this after I setup Mealie and created a mealplan with two entries, one dinner in todays date and then another dinner one day ahead.
I then navigated to the swagger docs page and tested the /api/households/mealplans/today endpoint
I set the TZ environment variables in the docker-compose.yml file to a timezone in the future(i.e. Australia/Sydney) and compared the result to the production build

[boc-the-git]

This looks fine to me, thanks @michaelclark2 !

@michael-genson what are your thoughts?
In particular I'm wondering if the following (the only other place to call get_today) should also be updated 🤔

mealie/mealie/services/scheduler/tasks/create_timeline_events.py

Line 32 in 613e4ef

mealplans = repos.meals.get_today()

[michael-genson]

@boc-the-git yeah we probably want to do this since DAILY_SCHEDULE_TIME uses local time as well

@michaelclark2 would you be able to update it here as well?