Development: Add endpoints for build agent information in local continuous integration

[laurenzfb]

Checklist

General

• I tested all changes and their related features with all corresponding user types 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 pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).

Motivation and Context

For admins, it might be interesting to get information on available build agents in local CI, e.g. number of build jobs currently running on an agent, build job capacity.

Description

This PR adds some REST endpoints to be later used for displaying build agent information on the client. Each hazelcast member adds itself to the list when the LocalCISharedBuildJobQueueService is initialized. The information is updated everytime a member processes a build job. When calling the endpoint, the list is updated to make sure that ex members who left the cluster will not be represented.

Steps for Testing

Prerequisites:

• 1 Instructor
• Programming exercise
• Postman, logged in as admin user

1. In Postman, GET /api/admin/build-job-queue/build-agents
   • On TS6, TS11 and locally, you should see one entry, on TS3 three entries (you might have to wait for a moments, until all nodes have registered)
   • numberOfCurrentBuildJobs should be 0 for all build agents
2. Create some submissions for the programming exercise
3. Check the endpoint again. Some build agents should have numberOfCurrentBuildJobs > 0

Testserver States

Note

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

Review Progress

Performance Review

• 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

[github-actions]

⚠️ Unable to deploy to test servers ⚠️

Testserver "artemis-test3.artemis.cit.tum.de" is already in use by PR #7764.

[mateusmm01]

Tested locally. Work as expected. Code also LGTM

[reschandreas]

demonstrated in testing session, works as expected. code also lgtm!

[RY997]

Tested in a testing session, worked as expected

[milljoniaer]

Demonstrated in small testing session, works as expected 🚀