Add new TestType enum values and update tests dropdown UI

[Copilot]

• Add 7 new TestType enum values to backend and frontend
• Update API docs (server/api.yaml) with new enum values (fix javaScript → javascript)
• Rename CoreEndTermInterview → CoreEndInterview in backend, frontend, and UI
• Update frontend UI: dropdown always shows only the 7 new test types
• Remove legacy test type conditional logic from dropdown (legacy types kept in enum for API/DB compatibility)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add new test enum values</issue_title>
<issue_description>## Requirements

1. Add a new values to TestType enum to both backend and frontend.
   • key: CoreMidTermInterview / value: core-mid-term-interview'
   • key: CoreEndTermInterview/ value:core-end-interview'`
   • key: FrontEndMidTermInterview / value: frontend-mid-term-interview'
   • key: BackEndMidTermInterview / value: backend-mid-term-interview'
   • key: CloudMidTermInterview / value: cloud-mid-term-interview'
   • key: DataMidTermInterview / value: data-mid-term-interview'
   • key: TesterMidTermInterview / value: tester-mid-term-interview'
2. Update API docs (api.yml) with the new values
3. Frontend: Add the enum values to the tests dropdown. And remove all existing value from the UI (keep them in the API for archive information and legacy support)</issue_description>

<agent_instructions>Make minimal required changes to fulfill the task.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Add new test enum values #309

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[stasel]

I made a mistake in the ticket, can you please rename the key to CoreEndInterview

[Copilot]

Done in b0e3093 — renamed to CoreEndInterview in both backend and frontend enums.

[stasel]

change the caption to Core end interview

[Copilot]

Updated in b0e3093 — caption is now Core end interview.

[Copilot]

Pull request overview

Adds seven new interview-type TestType enum values across the backend model, frontend types, and OpenAPI docs, and updates the test-type dropdown UI to show only the new options while keeping legacy values for archive/compatibility.

Changes:

• Added 7 new TestType enum values in both server and client type definitions.
• Updated server/api.yaml Test.type enum to include the 7 new values.
• Updated TestDetailsModal test-type <Select> options to only show the new interview types.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
server/src/models/Trainee.ts	Extends backend TestType enum with 7 new interview types.
client/src/data/types/Trainee.ts	Mirrors backend enum updates on the frontend type layer.
server/api.yaml	Documents the new Test.type enum values in OpenAPI.
client/src/features/trainee-profile/education/tests/TestDetailsModal.tsx	Replaces dropdown options to show only the new interview types.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[stasel]

There are two bugs:

Selection from the drop down no longer works.
When editing a legacy test, the default value in the dropdown is empty even though the existing value is rendered

[Copilot]

There are two bugs:

Selection from the drop down no longer works....

Fixed in ede348b. Both bugs had the same root cause: MUI's <Select> uses React.Children to find a matching <MenuItem> for the current value, but React.Children doesn't traverse into React Fragments (<>…</>). That caused the selected value to render blank and onChange to not fire. Replaced the fragments with keyed arrays so MUI can properly traverse the children.

[stasel]

Please remove all legacy tests from the UI (Keep them in the frontend UI).
If a user tries to edit a legacy test - it's ok to keep the drop down value empty and let it allow to select only new tests. There will be no future edits of a legacy test.

[Copilot]

Please remove all legacy tests from the UI (Keep them in the frontend UI).
If a user tries to edit a legacy test - it's ok to keep the drop down value empty and let it allow to select only new tests. ...

Done in c4f4843 — removed all legacy conditional logic. The dropdown now always shows only the 7 new test types. Legacy values remain in the enum for API/DB compatibility but are no longer referenced in the UI.