Ocrvs 6909

[Nil20]

No description provided.

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[Zangetsu101]

Let's make this a bit more generic as we know that custom events are coming. So the payload for the event could be something like this:

type EventPayload = {
  event: string
  jurisdictionId?: string
}

type IAdvancedSearchParam = {
  event: EventPayload[]
  ...
}

Notice how the jurisdictionId is optional here. So if a user has birth:search:my-jurisdiction, death:search scope, gateway will send something like

[
  { event: 'birth', jurisdictionId: '1234-4567' },
  { event: 'death' }
]

Then we can just map this array to the shouldMatchCondition