Adds conditional rendering of adhoc registration

[Sowmiya07]

Description

Summary

• Single registration page now supports both long-term and ad-hoc cycles via IS_ADHOC_CYCLE constant — no new routes
• Mentor fetch filtered by cycle type using ?mentorshipTypes=Ad-Hoc or ?mentorshipTypes=Long-Term

Changes

• IS_ADHOC_CYCLE constant added to mentorshipConstants.ts to toggle cycle type
• Schema: superRefine enforces mentorshipFocus ≥ 1 for all types; availableHsMonth ≥ 2 for long-term only and availableHsMonth > 1 for adhoc; adhocMenteeFormDefaultValues exported with Mentorship Type
• Step 1: hides available hours field for ad-hoc; removes mentorship type radio (driven by constant)
• Step 2: shows ad-hoc description variant; fixed duplicate error messages from child components
• Registration page: conditional step validation, breadcrumb, success message, and mentor fetch param per cycle type
• Tests: new menteeSchema.test.ts for conditional validation; adhoc suite added to page tests
• Adds isWomen dropdown to Form

Type

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

Related Issue

Screenshots

Registration Open and Its Long Term

Correct Available Hours validation
Mentorship Type is not shown

Dual Validation message not shown

Show only cycle relevant mentors

Adhoc

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.
• I have added a screenshot from the website after I tested it locally

[nora-weisser]

@Sowmiya07 , would it be possible to exclude mentor from the dropdown if he/she has been chosen as another priority?

[nora-weisser]

@Sowmiya07 , while testing I hit this problem of providing memberType: "memberTypes: At least one member type must be provided (e.g., Member, Volunteer, etc.)¨

It is a blocker for submitting the application.

[Sowmiya07]

@nora-weisser Exclusion of mentor, we can pickup later. I am afraid we don't have enough time now.

I tried submitting mentee registration and its working fine for me. I am testing with current main version. Can you please check if the backend code is up-to-date?

[nora-weisser]

I think that "Available hours per month" can be confusing for ad-hoc, as they will commit only 1 hour per month per 1 mentor. They have one-off session. Would be good to give it a thought and see if we can send 3 hrs in the payload, if the mentee applied for 3 mentors in the cycle. What do you think? @Sowmiya07

[IrynaLypnyk]

Approved from my side. I reviewed the main ad-hoc registration changes and they look aligned with what was discussed in the call. The NOSONAR/cognitive complexity refactor and backend-driven available mentors logic can be tracked as follow-up improvements.

I checked the failing CI. The failure seems to be in MenteeRegistrationPage.test.tsx because window.scrollTo is not implemented in jsdom. This looks related to the test environment rather than the production flow, but it would be good to mock/fix it before merging.

[dricazenck]

Please have a look in failing test, once is fixed I think all good to be merged.

[dricazenck]

this change break the test, so please update the tests, because it is based on the ad-hoc and it won't be showing this attribute anymore, please also update the screenshot with the latest changes.

Here it is the details of the test that is failing

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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