Feat/new restaurants api

[HenriqueSFernandes]

WIP implementation of the new restaurants API.
It includes changes that will be undone before the merge, such as changing the provider to always fetch from the remote and debug print messages.
Currently, the meals page includes every establishment from SASUP, but it uses the menu from the old Excel file.

Closes #1360
[Description of the changes proposed in the pull request. Include steps to replicate the behavior and screenshots if UI is updated]

Review checklist

• Terms and conditions reflect the current change
• Contains enough appropriate tests
• If aimed at production, writes a new summary in whatsnew/whatsnew-pt-PT
• Properly adds an entry in changelog.md with the change
• If PR includes UI updates/additions, its description has screenshots
• Behavior is as expected
• Clean, well-structured code

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 39 lines in your changes missing coverage. Please review.

Project coverage is 12%. Comparing base (bc5ba1c) to head (5b2568d).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #1393   +/-   ##
=======================================
- Coverage       12%     12%   -0%     
=======================================
  Files          265     265           
  Lines         7209    7223   +14     
=======================================
  Hits           806     806           
- Misses        6403    6417   +14     

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[HenriqueSFernandes]

It seems to be working with the meals hardcoded (using week 40), but there is a problem with saving the meals in the local storage. From what I can see, that problem already existed before.

When calling db.saveIfPersistentSession(restaurants):