Improve Attribute Filter Logic in Asset Comparison Table to Distinguish Between Digital States and Numeric Values

In PI Vision, when using dynamic search criteria in an Asset Comparison Table, attribute filters such as "Drive_G >= 15" can produce misleading results because PI Vision does not differentiate between digital states and actual numeric values. Digital states like "Pt Created" are stored as integer values (e.g., 253), which can overlap with valid numeric data. As a result, an asset with a Drive_G of 253 is displayed as "PT Created" rather than showing the numeric value, even though the intent of the filter was to capture numeric values only. This leads to confusion and incorrect display of data. Currently, users must manually exclude these digital state values by adding filters like "Drive_G ≠ 248" and "Drive_G ≠ 253", which is unintuitive and not scalable. A more robust filtering mechanism is needed to distinguish between digital states and true numeric values so that range filters behave as expected and do not require manual digital state exclusions.

This is similar to another request: https://internalavevapisystem.ideas.aha.io/ideas/PIVISION-I-132