Avoid mixups between different CPSes in ZenModeConditions

A couple of places in ZenModeConditions assumed that condition id uniquely determines ConditionProviderService, which is not correct.

Additionally, verify that only system zen rules can be handled by system CPSes (schedule, event, etc).

Bug: 391894257
Test: atest ZenModeConditionsTest
Flag: EXEMPT Bug fix
(cherry picked from commit 5cb0ae9c43e2262ad37f599de4c65bb31841f936)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5c4b6e07334a19bbc236e08b56b4bf2c6e1acc30)
Merged-In: I7bff4b04674b5f247bd3b8b6920af029ef8098f5
Change-Id: I7bff4b04674b5f247bd3b8b6920af029ef8098f5