Do not proceed with LocalEntitiesFilterStrategy filtering if instanceId is null

[grzesiek2010]

Closes #6378

Why is this the best possible solution? Were any other approaches considered?

We should check if instanceId is null and only if it is not should we proceed with LocalEntitiesFilterStrategy. When it comes to performing filtering on repeats it will be null and of course in this case LocalEntitiesFilterStrategy should not be used.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

It's a pretty safe change so testing the scenario described in the issue should be enough.

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[dbemke]

Tested with Success!

Verified on a device with Android 10

Verified Cases:

• issue Filter expression on a repeat crashes attempting to check applicability of Entities filter strategy #6378 doesn't occur
• quick regression checks in forms with repeats

[WKobus]

Tested with Success

Verified on device with Android 14