(frontend): add document type field on primary identification screen

[faiza-jahanzeb]

Summary

Work item: #14682
Add document type field on primary identification screen
User is presented with the Current Status options. Based on the correct options "Canadian citizen born outside Canada" or "Registered Indian born in Canada" in current status, the document type show respective options.
On pressing next button, field is validated. Correct validation for proof of concept is "Canadian citizen born outside Canada"

The document type is validated for null value.

Types of changes

What types of changes does this PR introduce?
(check all that apply by placing an x in the relevant boxes)

• 🛠️ refactoring -- non-breaking change that improves code readability or structure
• 🐛 bugfix -- non-breaking change that fixes an issue
• ✨ new feature -- non-breaking change that adds functionality
• 💥 breaking change -- change that causes existing functionality to no longer work as expected
• 📚 documentation -- changes to documentation only
• ⚙️ build or tooling -- ex: CI/CD, dependency upgrades

Checklist

Before submitting this PR, ensure that you have completed the following. You can fill these out now, or after creating the PR.
(check all that apply by placing an x in the relevant boxes)

• code has been linted and formatted locally
• added or updated tests to verify the changes
• added adequate logging for new or updated functionality
• ensured metrics and/or tracing are in place for monitoring and debugging
• documentation has been updated to reflect the changes (if applicable)
• linked this PR to a related issue (if applicable)

Linting and formatting

npm run lint:check
npm run format:check

Unit and e2e tests

npm run test
npm run test:e2e

[sebastien-comeau]

I'd need to experiment with it, but I think using a single validation and returning all errors to the component, even if the entire form isn't displayed, could work. The "step" logic might not be necessary.