Development: Refine user data export

[sachmii]

Checklist

General

• I tested all changes and their related features with all corresponding user types.
• 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) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines.

Motivation and Context

Closes #1695, needed to add interview data to user data export/

Description

• Added interviewee data to applicant export and interview process/slot data to staff export (no IDs included)
• Introduced new export DTOs for interview processes and interviewees; expanded interview slot DTO to include context fields without IDs
• Extended interview repositories with queries needed to fetch interviewees and slots with job context
• Updated export mapping logic to build interview process/slot data from fetched entities
• Adjusted user data export tests to cover interview data and assert IDs are not present in the JSON

Steps for Testing

Prerequisites:

1. Log in to TumApply as admin, professor and applicant
2. Check that user data export works and contains only user-specific data

Review Progress

Code Review

• Code Review 1

Manual Tests

• Test 1

Test Coverage

Warning: Server tests failed. Coverage could not be fully measured. Please check the workflow logs.

Last updated: 2026-01-22 17:55:55 UTC

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

@sachmii Test coverage has been automatically updated in the PR description.

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

🤖 No OpenAPI or client changes needed.

[Abi107717]

Thank you for implementing this 😊Code LGTM, Just small comments, is there are a reason, that you are using NON_NULL instead of NON_EMPTY?

[github-actions]

@sachmii Test coverage has been automatically updated in the PR description.

[github-actions]

🤖 No OpenAPI or client changes needed.

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.