Filter out TEIs with OMRS ids from being synced on WF1

[AishaHassen]

Background, context, and business value

The MSF workflows were design with the thinking that WF1 would run once and that would be it. But we are not discovering that WF1 might need to be rerun once per program to get DHIS2 patients from different programs to OMRs. This will mean that even patients in DHIS2 that originated from OMRS will be synced back to OMRS when WF1 runs.

What this issue needs to do, is filter out all TEI's that have an OMRS-id and exclude them from being synced to OMRS.

The specific request, in as few words as possible

1. Modify the Get Teis and Locations step of WF1

• Add logic in this step that filters out TEIs that we are getting fetched from DHIS2 where the OMRS-id in the attributes(attribute-id: "AYbfTPYMNJH") is not null.
• state.teis should only contain TEI's that do not have an OMRS-id

Testing Guidance

1. Set the cursor to 03-21-2025 and run WF1
2. the get TEIs should fetch TEI's including this one that has an OMRS-id
   Note: there is currently a bug that keeps erasing the OMRS-ids so if you are not able to find an OMRS-id for the TEI, try creating a new patient on OMRS and running WF2. then your new TEI created by WF2 should have the OMRS-id
3. Confirm that TEI's with OMRS-id do not get sent to subsequest steps for syncing

Credentials

1. DHIS2 LP - MSF DHIS2 UAT - June 2024
2. OMRS LP - MSF OpenMRS Demo - openfn user

Toggl

MSF 2025 - Additional Forms

Branch and project

1. Branch - main
2. Project - [msf-lime-mosul](https://app.openfn.org/projects/69066751-5f2c-459c-b42e-feba1c802383/w)

Pre-Development Checklist

Before handling this issue to a developer, ensure the following items are
checked:

• Credentials: Ensure all necessary credentials are available and
  documented.
• Sample Input Data: Ensure sample input data is provided and linked.
• PII: Verify if any Personally Identifiable Information (PII) is involved
  and ensure proper handling.
• Collections: Confirm if collections are needed and pre-configure with
  sample data if required. NA
• Mapping Spec: Ensure mapping specifications are complete and linked.NA
• API Docs: Ensure all relevant API documentation is linked.NA
• Workflow Diagrams: Ensure workflow diagrams are complete and linked.NA
• VPN Access: Ensure VPN Access is provided if required to run the workflowNA
• Toggl: Ensure the Toggl project name is provided.