As a user, I want an accurate and more concise representation of the labels signaling the purchase urgency

[yiremorlans]

Summary

Currently, the shopping list contains a legend with all the possible signals for a user to identify how soon they need to purchase an item in their list.

• "Soon" represents within 7 days
• "Kinda Soon" between 7 and 30 days
• "Not Soon" between 30 and 60 days
• "Inactive" been over 60 days since the last purchased
• "Not yet purchased" to show an item not yet purchased

Reduce the number of labels for the user to keep track of to only essential as outlined in issue #12. Also required to address the bug where a user adds an item to be purchased "Not Soon" being grouped with the "Kinda Soon" items.

Acceptance criteria

• The legend will have only four labels: Soon, Kinda Soon, Not Soon, and Inactive.
• Address the bug that is causing newly added "Not Soon" items to be grouped with the "Kinda Soon" category.

Notes

What functions are handling dates from our backend and how are they being rendered on the front end? Address any functions with similar behaviors. The proposed solution for incorrect grouping of items is to round up(Math.ceil) instead of down for getDaysBetweenDates. (Thanks @drakenguyen4000 )