Development: Regenerate Aeolus LocalCI build scripts

[b-fein]

@coderabbitai ignore

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.

Changes affecting Programming Exercises

• High priority: I tested all changes and their related features with all corresponding user types on a test server configured with the integrated lifecycle setup (LocalVC and LocalCI).

Motivation and Context

The Windfiles CI check kept failing in other unrelated PRs due to changes in the scripts, e.g. #8388, #8323:

7a8
> 
File ./src/main/resources/templates/aeolus/java/plain_gradle.yaml has changed

Description

Fixes the ‘Check if windfiles and scripts match’ CI step.

This PR ensures the additional final newlines in multiline strings are always removed.
I’m not sure why it started failing for only this case, as far as I can tell the multiline string block for plain_gradle.yaml looks the same as in the other build scripts.

Some of the build scripts already made use of the final newline removal (c/gcc.yaml on develop right now):

Artemis/src/main/resources/templates/aeolus/c/gcc.yaml

Line 28 in 2ce2dd7

script: |-

Therefore, this is supported by Aeolus. This PR unifies the behaviour across all build scripts.

Steps for Testing

Code review is enough. As you can see there, only empty lines are removed in the generated shell scripts.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Code Review

• Code Review 1
• Code Review 2

[pzdr7]

Code