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

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 4.34783% with 88 lines in your changes missing coverage. Please review.

Project coverage is 12%. Comparing base (1002364) to head (af50845).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #1393   +/-   ##
=======================================
+ Coverage       12%     12%   +1%     
=======================================
  Files          264     264           
  Lines         7245    7270   +25     
=======================================
+ Hits           803     807    +4     
- Misses        6442    6463   +21     

[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):

[HenriqueSFernandes]

The new menu's API has been implemented.

Due to the current front-end implementation restrictions, the old Restaurant model was used, but the new UI will use the more complete Establishment model by @thePeras.

The loadFromStorage function in the restaurant_provider was changed so as not to cause a crash. The commented code should be reimplemented after issue #1370 is fixed.

Special thanks to @AugustoVSoares for the collaboration on this implementation.

[HenriqueSFernandes]

The distinction between lunch and dinner is hard coded, so it always displays "Almoço / Jantar" regardless of the app's language setting.
I propose discussing in the next meeting whether this should be addressed now or postponed until the new UI is implemented. Personally, I suggest waiting for the new UI, as the fix would not be necessary.

[HenriqueSFernandes]

As discussed in today's meeting, I added the English names for the meals

Feel free to suggest more changes.

[thePeras]

Incredibly work!! It's so nice to see this finally in UNI.

After this detail, it's ready to 🛫

[thePeras]

Because you modify the database table, increase its version. Since it's stills in v1, you need to create migration code. Look at #1380