Lear API: Need Entity Status

### Entity Status
## Description:

The Coops UI expects a "status" property from the "GET /api/v1/businesses/:id" endpoint. The expected values are:
- GOODSTANDING
- PENDINGDISSOLUTION
~~- NOTINCOMPLIANCE - reviewing this option not for MVP~~

The above is already implemented (on a preliminary basis) in Microcks.

There will be no hard feelings if the UI needs to be updated for different statuses (or removed if entity status is not a thing).

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed
- [ ] What are the dependencies
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required

Acceptance / DoD:
- [ ] Design / Solution accepted by Product Owner
- [ ] 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