feat: add new schedule api

[limwa]

Closes #1254.
Closes #1280.

Implements behavior to retrieve a user's schedule from the new schedule API.
For now, it reads the HTML from the schedule page and uses the information to retrieve the schedule data from the API.

Removes the old HTML parsing code.

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

Project coverage is 16%. Comparing base (d460c06) to head (8e43723).
Report is 5 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #1281   +/-   ##
=======================================
- Coverage       16%     16%   -0%     
=======================================
  Files          233     239    +6     
  Lines         7220    7172   -48     
=======================================
- Hits          1139    1078   -61     
- Misses        6081    6094   +13     

[thePeras]

Looking into the code, seems very nice!

1. Can we put the response models inside a specific folder? ex lecture_response
2. Are we keeping the old api code?

[limwa]

1. Can we put the response models inside a specific folder? ex lecture_response

The response models are already inside the models folder in the new_api directory, so I don't understand what you mean by a "specific folder". Can you please elaborate on that?

2. Are we keeping the old api code?

I was under the impression we were, but I'm happy to remove it 😄
Personally, I think it might be too soon to rely on this new API at 100%. We can reconsider this later this year...

[thePeras]

The response models are already inside the models folder in the new_api directory, so I don't understand what you mean by a "specific folder". Can you please elaborate on that?

Sorry, I miss looked the folder. It's nice this way!

2. Are we keeping the old api code?

I was under the impression we were, but I'm happy to remove it 😄 Personally, I think it might be too soon to rely on this new API at 100%. We can reconsider this later this year

It seems pretty solid, but am not opposing of keeping

[thePeras]

I don't have schedules to test, but it seems good to me.
Nice work and what a pleasure to see so much code deleted!

✅ 🛫

[DGoiana]

Well done! 🚀