Added SCEvents ability to create event

[maernest04]

PR for issue 2068

Added Clark UI and wiring for SCEvents: officers and admins can open the events page and use a create event flow that talks to the SCEvents HTTP API. Submitted events are stored by SCEvents in its own MongoDB (scevents / events), not Clark’s main API database.

• API client (src/APIFunctions/SCEvents.js): getSCEvents, createSCEvent, configurable base URL via - REACT_APP_SCEVENTS_URL (with a local dev fallback).
• Pages: Events.js (listing + Create CTA for officers/admins), CreateEventPage.js + CreateEventFormQuestionBlock.js (form aligned with SCEvents event/registration payload shape).
• Routing: Registered /events and /events/create in Routes.js with OFFICER_OR_ADMIN access for the create route.
• Nav: Admin sidebar links for SCEvents and Create event when config.SCEvents.ENABLED is true (AdminNavbar.js).
• Auth: Create-event access is officer or admin (consistent with other officer/admin tools), not admin-only.

Screenshots of what this would look like

[steeevin88]

could we do a few things:

1. link the issue that this resolves in the PR description (let's always do this in the future!)
2. i merged Trista's PR that adds the page contents; can you fix the merge conflicts? we should be keeping her UI + just add your button somewhere (similar to what you did with the blank page)
3. you mentioned the port conflicts + it makes sense; let's make the default port for SCEvents something else... i think we should make it 8002 (b/c SCEta is 8001, and Cleezy is 8000?). Can you double-check this, and then open a new PR in the SCEvents repo to change the default port? This means changing the default gin server setup to use port 8002 instead of the default, and changing the port mappings in the docker-compose as well. In the end, the server should run in its Docker container's port 8002, and we will map it to our local port 8002. lmk if this doesn't make sense

i'll give a closer review after these changes, but had a few questions from a brief look:

• why is there an SCEvents tab in the admin page? and a separate Create Event one? if the SCEvents tab leads to the events page let's just remove it so we don't bloat the admin panel (if we need to navigate to it we can manually change the URL ourselves)
• let's get rid of the base url logic and just assume it's the localhost port, i don't think we'll ever be doing the .env approach

[steeevin88]

big pr so i will probably re-review 😅

could we also increase the padding here?

[steeevin88]

left some small comments but lgtm

please resolve all the comments once done + ping me again before we merge

[steeevin88]

left a reply on one of the above comments but otherwise lgtm 😄

please resolve all the other comments so this PR is less cluttered, we can merge after

[KhoaNguyen706]

LGTM

[steeevin88]

re-reviewed

[steeevin88]

nice!