Allow counters with lower priority (calculated earlier) to be used within evaluation conditions of higher priority counters

Use case: Users of Safer Payments have the ability to calculate the most common value of a reference attribute. For example, understanding a cardholder's most common grocery store merchant ID is a great way of reducing false/positives. Because many consumers tend to transact at the same handful of grocery stores (gas stations is another good example), it could be valuable to know the cardholders top n reference ID values. Without the ability to reference the 1st most common grocery store within the evaluation conditions, users do not have the ability to calculate the 2nd, 3rd, 4th, etc most common grocery store.

The evaluation conditions would be written as such: Merchant Identifier not equal to {C_Most Common Grocery Store}.

Safer Payments does allow the above today, but only for counter attributes that are stored. However, because C_Most Common Grocery Store would be calculated for the current transaction earlier in priority, it should not be required that C_Most Common Grocery Store be a stored attribute. It is held in CDC and there is no need to reference the attribute historically. Rather, we want to reference the historical Merchant IDs and compare them against the "Most common value" that has been computed for the current transaction. In this sense, the system should only allow the attribute to be selected in the value dropdown (when curly brackets are entered) and not allow the user to select the value in the attribute picklist.