34022 move director mailing validation to schema

[mruff-aeq]

Issue #: /bcgov/entity#34022

Description of changes:
Removed the CORPS-only director mailingAddress presence check from legal-api since that validation now lives in the schema (directors.json requires mailingAddress); the deps temporarily reference my fork of business-schemas for pre-merge testing and will be pointed back to bcgov once the schema PR is merged and tagged.

Testing

curl -sS -i -X POST \
  "http://127.0.0.1:5000/api/v2/businesses/CP0000019/filings?only_validate=true" \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-apikey: KHGuiTxG52ejzFZi7wu4QyD8GdVGEMAz" \
  -H "account-id: 3040" \
  -H "Content-Type: application/json" \
  --data-binary @B_missing_mailing.json

Raw response:
HTTP/1.1 422 UNPROCESSABLE ENTITY
Content-Type: application/json
API: legal_api/3.1.0
SCHEMAS: registry_schemas/2.18.74
Connection: close

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the lear license (Apache 2.0).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mruff-aeq]

Closing — tech-debt cleanup blocked. Can't move mailingAddress to schema (shared director def, no legalType to scope by; would reject existing coop directors). Not worth pursuing.