Non Civic Addresses

Might be related to #13486 . Linked for reference.

There are homes that don't have civic addresses. We an extra field to provide information for non civic addresses.

### User story
As a registries staff member
I want to be able to free-form enter a non-civic address
So that I can complete a filing for people that:
* Don't have a regular civic address that can be verified by Canada Post
* Don't have a PID
* Don't have a manual description of a civic address
* Possibly have a really long address

### Questions
* Should this change apply to all address fields?
### 🏞️ Non-Civic Address Entry

The system must support the entry of non-civic addresses for manufactured homes located in remote or unstructured locations. This includes areas without a PID or legal land description, such as forestry roads or undeveloped land. Sometimes, the available information may be just a GPS location.

#### Requirements:
- A new location type option (e.g., **“Non-Civic Address”** or **“Other Location”**) must be available in the UI.
- When selected, a **free-form text field** must appear allowing detailed location descriptions (e.g., GPS coordinates, landmarks, distance from known points).
- The system **must not require** PID or legal land description when this option is used.
- The entered data must be **stored and retrievable** for reporting and updates.
- The solution must be applied **globally across all workflows** where address entry is required.

Review the related issue #13486 and the existing address-entry workflows first. Confirm which address fields and workflows are in scope, then define completion as supporting a selectable non-civic location, free-form details without PID or legal-land requirements, and persistence for reporting and updates.

Written by the indexing model from the issue text.