feat: add mentorship cycle status page to admin app (#785)

[wilsonadenuga]

Description

Adds a Cycles page to the admin app at /admin/mentorship/cycles, so the mentorship team can move cycles through their lifecycle without calling the API directly.

• Lists the current year's cycles in a table (cycle, type, registration dates, run dates, status), styled like the Mentees page.
• Type and Status filters narrow the table. They filter the cycles already loaded, so no extra API calls.
• Each row has a status select. Picking a new status opens a confirm dialog showing the change (e.g. OPEN → CLOSED) and what it means. Confirm calls the API, Cancel keeps the current status.
• On success the row updates in place and a success alert is shown. API errors (e.g. Invalid status transition from 'DRAFT' to 'COMPLETED') are shown inline as an error alert.
• A Cycles nav link is added to AdminLayout for ADMIN and MENTORSHIP_ADMIN, the same guard as the Mentorship link.

Endpoint	Used for
GET /api/platform/v1/admin/mentorship/cycles/all?year={current year}	Loading the table
PATCH /api/platform/v1/admin/mentorship/cycles/status?cycleId={id}&status={status}	Confirming a status change

Notes:

• Merge after feat: add optional year filter to admin cycles list (#800) #803. The year filter comes from feat: add optional year filter to admin cycles list (#800) #803. Until it is merged the backend ignores ?year= and returns cycles for all years.
• The design differs slightly from the issue: cycles are shown in a table with a status select per row instead of a cycle dropdown, filters were added, and status changes go through a confirm dialog because they cannot be undone (COMPLETED and CANCELLED are final, and OPEN/CLOSED change public registration).
• The status select lists all six statuses. Allowed transitions stay in the backend, and any rejected move shows the API's error message.

Related Issue

Closes #785

Change Type

• Bug Fix
• New Feature
• Code Refactor
• Documentation
• Test
• Other

Screenshots

Cycles table

Status filter (Draft)

Confirm dialog

Pull request checklist

Please check if your PR fulfills the following requirements:

• I checked and followed the contributor guide
• I have tested my changes locally.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dricazenck]

🚢