course management data-providers refactor

[mono424]

Motivation and Context

Currently, the course management relies on Go generated template data. This means we need page reloads and also it is not good practice to have backend and frontend entangled in that way. Further, much very specific code is used to handle the course management tasks, that could be abstracted in cleaner ways.

Description

This PR untangles backend and frontend by using data-providers that are introduced earlier and are already used for data-sections and other parts of the app. This gives a standardized abstraction to handle the lecture's client side. Also, this will prevent useless page reloads and give a better standardized and app-global API to create new lectures, fetch or update them.

Steps for Testing

• Go to course management Page
• Open a course
• Edit a lecture
• a) Check uploading media
• b) Check changing meta data
• c) Check uploading attachments (Drag and drop Description field)
• Check JS-Console and Network Tab for errors
• Reload and check if data is persistent

Screenshots

Way shorter UI specific code (edit-course.ts):

[github-actions[bot]]

Your Testserver will be ready at https://1137.test.live.mm.rbg.tum.de in a few minutes.

Logins

| Kurs1 | Kurs2 | Kurs3 | Kurs4 | | ---------------------------------------- | ------------------------- | ------------------------- | ------------------------- | | public | public | loggedin | enrolled | | prof1 | prof1 | prof2 | prof1
prof2 | | student1
student2
student3 | student1
student2 | student2
student3 | student1
student2 |

[mono424]

Changes look good.

Somehow the "Delete Lecture" in the dropdown menu doesn't work anymore. (Console: ReferenceError: Can't find variable: deleteLecture) 😅

thanks for the ping! Should have tested better, delete and deleteSeries should be fixed now ;)

[mono424]

@joschahenningsen regarding the size of the pr do you want to take a look first before I merge or can I just go ahead and merge it?