Tech Debt: Use Nx Release to create versioned releases

### Description:

We currently use Release-it to tag and cut our releases. We can utilize Nx's release procedure to do the same but with awareness of the Monorepo.

See https://nx.dev/features/manage-releases

### Acceptance Criteria:

_I want_ to use Nx CLI's `release` command to cut releases
_because_ it is aware of the monorepo structure
_and this will help me to_ cut releases for all projects at once.

### Development Checklist:

- [ ] Add `release` section to `nx.json` with config comparable to Release-it's
- [ ] Specify only Apps to be released
- [ ] Update `Makefile`'s `release` target to utilize `nx release`
- [ ] Remove Release-it from deps

#### Resources

- https://nx.dev/features/manage-releases

**Definition of Ready** (Note: If any of these points are not applicable, mark N/A)

- [ ] ~~User story is included~~
- [ ] ~~User role and type are identified~~
- [ ] Acceptance criteria are included
- [ ] ~~Wireframes are included (if required)~~
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

·**Definition of Done** (Note: If any of these points are not applicable, mark N/A)

- [ ] Acceptance criteria are tested by the CI pipeline
- [ ] UI meets accessibility requirements
- [ ] Configuration changes are documented, documentation and designs are updated
- [ ] Passes code peer-review
- [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
- [ ] Ticket is ready to be merged to main branch
- [ ] Can be demoed in Sprint Review
- [ ] Bugs or future work cards are identified and created
- [ ] Reviewed and approved by Product Owner

Start with nx.json, the Makefile's release target, and the current Release-it configuration; then read the linked Nx release documentation. Done means the release target uses Nx CLI to create versioned releases for the intended apps, with comparable configuration and Release-it removed from dependencies.

Written by the indexing model from the issue text.