Summary

Adds the zod validation schema for the Institutional Representative Page. In addition, like verbally discussed in our meeting - if it ends up being possible for institutions outside of Canada to collaborate on projects, the country text box is now a dropdown instead, which displays various countries and territories.

Related Issues

• Form Validation - Institutional Rep Page #162

Description of Changes

Special Instructions

You may need to (re)build the @pcgl-validation package which contains the zod validation schemas before running the project

# in the root of the project folder
pnpm build:all

UI

• Adds a drop down for country selection as discussed in our meeting (to both applicant info and institutional info pages), however this can be disabled if not needed.
  • The browser unfortunately does not have a standard list for this, so the country list is pulled from the Government of Canada's Data Reference Standard on Countries, Territories and Geographic areas. With all countries, territories, and geographic areas labeled as ACTIVE used. Both English and French names are stored.
  • This data is licensed under the Open Government License - Canada license, as noted in the comment above the constant.
  • On selection of a country, the countries ISO3 code (example: CAN) is the value provided to save into the DB. Canada is selected by default.
• Standardizes the personal title drop down.
• Adds institutional representative page validation schema to the packages/pcgl-validation/src/schemas.ts file which validates inputed text according to the spec.
• Enables the use of browser-level auto-complete in our text fields. This is a accessibility best practice (see here: https://design-system.service.gov.uk/patterns/names/#:~:text=Use%20the%20autocomplete%20attribute%20on%20name%20fields)
• Fixes a bug where edit button wouldn't direct properly to app edit page.

Readiness Checklist

• Self Review

  • I have performed a self review of code
  • I have run the application locally and manually tested the feature

• PR Format

  • The PR title is properly formatted to match the pattern: #{TicketNumber}: Description of Changes
  • Links are included to all relevant tickets

• Labels Added

  • Label is added for each package/app that is modified (api, ui, data-model, etc.)
  • Label is added for the type of work done in this PR (feature, fix, chore, documentation)

• Local Testing

  • Successfully built all packages locally
  • Successfully ran all test suites, all unit and integration tests pass
  • 

• Updated Tests

  • Unit and integration tests have been added that describe the bug that was fixed or the features that were added

• Documentation

  • All new environment variables added to .env.schema file and documented in the README
  • All changes to server HTTP endpoints have open-api documentation
  • All new functions exported from their module have TSDoc comment documentation