213 candidate view application

[ostepan8]

Issue: closes #213

Description:
added the applicant view of their application. it's basically the same as the
admin view but read-only so applicants can't edit anything.

• created CandidateViewApplication container that reuses the same components
  as the admin view but passes isAdmin={false} to disable editing
• added getCandidateInfoByEmail to the api client so we can look up a user's
  appId from their email
• wired up the /candidate/view-application route behind the auth and role
  guards
• fixed the navbar links for standard users to actually point to real routes
  instead of hash anchors
• added dev auth bypass env vars (VITE_DEV_AUTH_EMAIL,
  VITE_DEV_AUTH_USER_TYPE) so we can test locally without cognito set up

Verification:

1. add VITE_DEV_AUTH_EMAIL=janedoe@gmail.com and
   VITE_DEV_AUTH_USER_TYPE=STANDARD to your .env
2. start the frontend with npx nx serve frontend
3. go to localhost:4200 — it should skip login and go straight to
   /candidate/view-application
4. check that the sidebar shows "my application" and "my forms"
5. check that the availability table has no edit buttons
6. scroll through and make sure all sections show up (school affiliation,
   availability, uploaded material, course requirements, question frames)
7. remove the VITE_DEV_AUTH_ env vars and confirm the login page shows up
   again

Future Work / Notes:

• CandidateInfoModule isn't registered in app.module.ts on the auth branch yet
  so the real api call to get candidate info by email won't work until that's
  added
• backend controllers have jwt auth guards so the full flow needs cognito
  configured end to end
• the dev auth bypass and mock data in CandidateViewApplication should get
  removed once cognito is actually working
• the design mockup has a blue header section with the applicant's name,
  pronouns, status pills etc that doesn't exist in the admin view either —
  probably a separate ticket