Fixes #16591 - Correct parameter value order for complex matcher
If the order includes more specific complex matchers before less specific one (e.g., "organization,location" before "organization"), the order of resolution is incorrect, because the classification service will check for the index of the matcher in the path which is serialized as a string - "organization,location\norganization" leading to incorrect order.
Related issues
Bug #16591: Smart matchers with multiple, more specific facts match on less specific facts
Fixes #16591 - Correct parameter value order for complex matcher
If the order includes more specific complex matchers before less
specific one (e.g., "organization,location" before "organization"), the
order of resolution is incorrect, because the classification service
will check for the index of the matcher in the path which is serialized
as a string - "organization,location\norganization" leading to incorrect
order.