Feat/fix ingredients

[mdeekshita]

Description

editing the food log for after you log in to be more user friendly, etc

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• [ x] New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (code improvement without changing functionality)
• Documentation update
• Configuration/infrastructure change
• [ x] Performance improvement
• Test coverage improvement

What Changed?

• changed the ingredients to make it more user friendly

Testing & Validation

How this was tested

1. I used the simulator to test and show

Screenshots/Recordings

Unfinished Work & Known Issues

• None, this PR is complete and production-ready
• [ x] The following items are intentionally deferred:
  • My specific tasks for this PR are all good and correct but there are some API calls that are bugging that would need to get fixed later on

Pre-Merge Checklist

Code Quality

• [ x] Code follows the project's style guidelines and conventions
• [ x] Self-review completed (I've reviewed my own code for obvious issues)
• [ x] No debugging code, console logs, or commented-out code left behind
• [x ] No merge conflicts with the base branch
• [ x] Meaningful commit messages that explain the "why"

Testing & CI

• [ x] All CI checks are passing
• [x ] All new and existing tests pass locally
• [ x] Test coverage hasn't decreased (or decrease is justified)
• [ x] Linting passes without errors

Documentation

• [ x] Code is self-documenting or includes helpful comments for complex logic
• [ x] API documentation updated (if backend endpoints changed)
• [ x] Type definitions are accurate and up-to-date

Reviewer Notes

• API calls failing after the fact

[Jrodrigo06]

LGTM

[Jrodrigo06]