[Satellite6] Wrong smart variable matcher applied when a parameter is in a compound matcher and also standalone

Issue

• overriding a smart variable using prioritized attribute order
• that ordering uses compound attributes like: attributeA,attributeB (higher preference) as well as standalone attributeA(lower preference)
• for a host matching both matchers for the compound and standalone attribute, the standalone one is applied - despite it has lower priority