Allow "Browser" (and other standard dimensions) as criteria in Bot Rules

Currently, Adobe Analytics custom bot rules only support filtering based on User-Agent, IP Address, or IP Range. However, when modern browsers (like Chrome or Edge) send requests without Client Hints, Adobe replaces the un-vetted minor version with a .999 placeholder in the reporting backend (e.g., Chrome 148.999), which is surfaced via the standard Browser dimension.

Because this fallback logic happens downstream from the initial User-Agent ingestion, we cannot reliably capture or block these specific spikes using standard User-Agent string matching in our Bot Rules.

Why this is needed: A sudden spike in .999 browser versions is a strong indicator of low-quality or bot traffic. However, our data quality is currently suffering because we have no native way to translate this specific reporting dimension back into a bot filter rule. Relying on complex VISTA data engineering or shifting IP ranges is inefficient for dealing with browser-specific anomalies.

Proposed Solution: Expand standard Analytics Bot Rules capability to include the processed Browser dimension (and potentially other processed dimensions) as an evaluation criterion, rather than limiting it purely to the raw User-Agent string. This will allow administrators to immediately isolate and filter out suspicious browser anomalies dynamically.