Iris: Replace or remove unnecessary client dependencies

[bassner]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
• I followed the coding and design guidelines.
• Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.

Motivation and Context

The IRIS UI is currently using these dependencies:

• angular2-draggable: Used to move and resize the chat window. Can be replaced with already used interact.js.
• angular-animations: Provides a predefined animation. We don't need that at all
• css-element-queries: Used to monitor the resizing of the chat window and storing the values in local storage. We don't need that at all

Description

Remove or replace dependencies as described above.

Steps for Testing

Prerequisites:

• 1 Student
• 1 Programming Exercise with IRIS enabled on TS9

1. Go to the exercise view
2. Open the chat window
3. Verify that you can drag the window around
4. Verify that you can resize the window on all edges
5. Verify that it expands to 95vw and 85vh if you click the fullscreen icon
6. Verify that it reverts back to default if you click it again
7. Verify that the icon automatically changes if you manually drag the window larger than 95vm and 85vh

Review Progress

Performance Review

• I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
• I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Exam Mode Test

• Test 1
• Test 2

Test Coverage

Screenshots