Development: Change client builder from browser esbuild to application

[pzdr7]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

In #6546, during the switch to Angular 16, we changed the production builder to browser-esbuild. This builder's schema lacks the loader option that will be required to integrate the Monaco editor into Artemis (#8130). By switching to the preferred application builder (that also uses esbuild), this becomes possible.

Description

The changes follow the instructions for migrating to the application builder.

Since SSR does not affect us, I have configured the outputPath property to output to the same directory as before (sets outputPath.browser to "" - see also this issue in the Angular repository)

Steps for Testing

Verify that Artemis can still be deployed to a test server and that the client does not break.

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

Manual Tests

• Test 1
• Test 2

[dmytropolityka]

seems to work as expected, tested both locally and on ts3

[milljoniaer]

code looks good to me 👍

[Kroko-fant]

Migration looks good to me

[basak-akan]

Tested locally, client does not break works well