Programming exercises: Support python exercises for local continuous integration

[laurenzfb]

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.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
• I followed the coding and design guidelines.
• I added multiple integration tests (Spring) related to the features (with a high test coverage).
• I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
• I documented the Java code using JavaDoc style.

Changes affecting Programming Exercises

• I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
• I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

With this PR, the local CI system supports Python exercises.

Description

I added Python options for the build script generation. Test results get parsed accordingly.

Steps for Testing

Prerequisites:

• 1 Instructor
• 1 Student
• Local VC CI test server (3 or 6 (GitHub), 11 (old server))

1. As instructor, create a programming exercise with Python
2. Template and solution build result should be as expected
3. As student, create submission for this exercise
4. Build results should be as expected

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

Test Coverage

Screenshots

[Hialus]

Left some small comments for the code.
Also if this is not done yet: Since you have to add support for new programming languages at multiple places, it would make sense to document these places somewhere in the artemis docs for future reference by other devs.

[Hialus]

Please notify me once this PR was merged, so I can adjust TS3 and TS6 for this change

[tobias-lippert]

Tested in testing session. Python exercise compiled successfully.

[max-bergmann]

Tested in testing session. Py compiled.

[laurenzfb]

Thank you for the code review @Hialus! I implemented your suggested changes. Concerning the documentation for future developers, I will do this in a follow up PR.

[tobias-lippert]

Reapprove, latest changes look good

[max-bergmann]

reapprove - lgtm