TES-80 fix: API response data structure

[WitchDevelops]

• adopted frontend to new shape of API response
• changed global types for product
• extra class in httpService for when the data is an object, not an array
• fixed test
• fixed ProductGrid
• adjust rendered colors for purple vs lavender (todo: remove the purple from the db)
• added fallback image:

[netlify[bot]]

✅ Deploy Preview for telia-web-shop ready!

Name	Link
🔨 Latest commit	b5823e1504dbd8df8fcd230b3c35120f929822d2
🔍 Latest deploy log	https://app.netlify.com/sites/telia-web-shop/deploys/66fc55e7cd5fe8000861a3ed
😎 Deploy Preview	https://deploy-preview-30--telia-web-shop.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 70 Accessibility: 100 Best Practices: 83 SEO: 92 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[KozerT]

🟢 This code is looking really good! 👍 I especially like how you've utilized types effectively . The enhancements to the test cases are also a big plus. 🟥 Prettier checks are failing. We need to reformat " npm run format " before pushing To make this code even more solid, we can:

Reduce redundancy: The getObject and getAll functions are quite similar. Error handling: Adding a catch block to the API calls (getObject) would provide a safety net for any future error handling needs.