Feat: placeOfEvent

[tareq89]

issue: #11148

Add placeOfEvent Resolution and Indexing Support

This pull request adds full support for resolving and indexing the placeOfEvent value for events.
The value may come from configured form fields or fall back to createdAtLocation.

---

What's Included

1. resolvePlaceOfEvent() Implementation

• Iterates over config.placeOfEvent fields in priority order.
• Respects conditional field visibility.
• Supports:
  • DOMESTIC address fields (resolves administrativeArea).
  • Location-type fields (resolves UUID directly).
• Falls back to eventMetadata.createdAtLocation when no valid field value exists.

2. EventConfig Validation

• Ensures place-of-event fields are valid and supported.
• Rejects non-location field types.
• Provides clearer error messages.

3. Elasticsearch Indexing Support

• Adds placeOfEvent mapping consistent with createdAtLocation.
• Supports location hierarchy expansion.
• Updates ES fixtures and mapping definitions.

4. Test Coverage

Includes tests for:

• Domestic address resolution.
• Location field resolution.
• Conditional visibility handling.
• Fallback behavior.
• ES indexing and search behavior.

---

Breaking Changes

• Invalid placeOfEvent configurations now throw validation errors.
• ES search results now consistently reflect the resolved location ID.

[makelicious]

Very nice 👍 Left few comments to clarify

[ocrvs-bot]

Your environment is deployed to https://ocrvs-11148.e2e-k8s.opencrvs.dev

[makelicious]

If event happens in an office that is at the top level, what will the array include? Could we ensure that other office worker with administrativeArea jurisdiction actually finds these?

Since they refer to NULL I'm wondering should it actually be part of the array 😬

[tareq89]

If event happens in an office that is at the top level, what will the array include? Could we ensure that other office worker with administrativeArea jurisdiction actually finds these?

Since they refer to NULL I'm wondering should it actually be part of the array 😬

The array will only include the location id, one item.

I think it is upto us how office worker with administrativeArea jurisdiction actually finds these, it depends how we interprete a location heirarchy with one locationId.