COLIN/LEGAL-API: tests for legal updater endpoints

### Replace_With_Short_Descriptive_Name
## Description:
- tests surrounding colin-api/legal-api are missing for legal-updater calls (postman + pytest)

**Dependencies**

**Acceptance Criteria**

**Validation Rules**

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed (full flow of business rules, happy and alternate paths etc.)
- [ ] What are the dependencies
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required
- [ ] Acceptance Criteria well defined in tickets (Story level) QA can confirm or deny
- [ ] Reference BA checklist for this story (functional description captured ?)

Acceptance / DoD:
- [ ] PR to remove feature flags created
- [ ] Check Requirements against completed stories
- [ ] Completed stories verified in Dev/Test/Prod
- [ ] Confirm Test cases built and succeeding
- [ ] Confirm successful End-End runs
- [ ] No regression
- [ ] All Linters passed
- [ ] Test coverage and Test ID acceptable by Product owner
- [ ] Ticket merged to master or story branch
- [ ] Add / maintain selectors for QA purposes
- [ ] Add PR numbers - If available
- [ ] All tests passed (Jest, Pytest, Postman)
- [ ] Developer to list Config changes/ Update documents and designs
- [ ] Design / Solution accepted by Product Owner
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed

Start by locating colin-api/legal-api and any existing Postman or pytest tests around related endpoints. Add coverage for the legal-updater calls and confirm the relevant Postman and pytest tests pass.

Written by the indexing model from the issue text.