Chore: handle mealie API change

[joncrangle]

Proposed change

Mealie is introducing breaking API changes that are already merged in the "nightly" builds. See https://github.com/mealie-recipes/mealie/pull/3970. The groups/statistics endpoint is being deprecated and replaced with a households/statistics API.

I modelled the API handling on the Immich implementation https://github.com/gethomepage/homepage/pull/2284. If the version starts with "v2", or equals "nightly" it will use the new endpoint. Otherwise, it will keep using the existing endpoint to ensure this is non-breaking for people who pin to a v1 build.

Closes #

Type of change

• [ ] New service widget
• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Documentation only
• [ ] Other (please explain)

Checklist:

• [x] If applicable, I have added corresponding documentation changes.
• [x] If applicable, I have reviewed the feature and / or service widget guidelines.
• [x] I have checked that all code style checks pass using pre-commit hooks and linting checks.
• [x] If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

[github-actions[bot]]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.