Optimize scan filtering

[twyatt]

Closes #889

Optimizes scan filtering when non-native filter(s) are combined with native filter(s), by favoring native scan filtering and moving non-native supported filters to flow filtering.

Take the following example:

Code	Graphical representation
filter { match { service = listOf(Filter.Service(B)) // AND name = listOf(Filter.Name.Prefix("A_")) // AND serviceData = listOf(Filter.ServiceData(..)) } }

This PR will optimize the scan by establishing a native filter for the Filter.Service and Filter.ServiceData and having the Filter.Name.Prefix filtering occur via flow operator.

Before the PR	After the PR

This optimization is only possible when a single match is specified (i.e. filters will not be OR'd). This is because when there are multiple filter match declarations, then it would be difficult to reliably determine which native filter was applied to know what "overlayed" filters should occur at the flow operator level. To illustrate this limitation, take the following example:

Code	Graphical representation
filter { match { service = listOf(Filter.Service(A)) // AND name = listOf(Filter.Name.Prefix("A_")) } // OR match { service = listOf(Filter.Service(B)) // AND name = listOf(Filter.Name.Prefix("B_")) } }

Then, during a scan there isn't a clear way to filter at the flow operator:

As such, for these situations (more than one match with non-native filters): all filters will occur at the flow operator level.

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

kable-core/src/androidMain/kotlin/BluetoothLeScannerAndroidScanner.kt:164

• Combining multiple native filters into a single ScanFilter may inadvertently merge distinct filtering criteria. Please review if this merging accurately reflects the intended native filtering behavior.

native = listOf(nativeFilters.values.toList().toNativeScanFilter()),