Feat/adhoc application flow

[Sowmiya07]

Description

• AD_HOC mentee applications are created directly in MENTOR_REVIEWING status, bypassing the admin approval step
  • acceptApplication delegates to MentorshipMatchingService.confirmMatch() for AD_HOC cycles, moving directly to MATCHED
  • confirmMatch validates expected status based on cycle type: MENTOR_REVIEWING for AD_HOC, MENTOR_ACCEPTED for LONG_TERM
  • Mentor is notified via sendNewMenteesNotification at registration time for AD_HOC (mirrors approveApplication behaviour for LONG_TERM)
  • TODO added on MentorshipMatchingService injection in MenteeWorkflowService to flag cyclic-dependency risk for future
    refactor

Related Issue

#712

Change Type

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

Screenshots

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