fix(attribute-values): Handle boolean attributes

[wmak]

• The endpoint allows attribute values but currently breaks because it makes some assumptions where the value would be a string. This fixes those cases so that we can use this endpoint for booleans

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5928272. Configure here.}

[sentry]

Bug: The code uses f.has() on the attributes_bool map, which translates to an incorrect ClickHouse function (has() instead of mapContains()), causing query failures.
_{Severity: HIGH}

Suggested Fix

Replace the call to f.has(column("attributes_bool"), name) with f.mapContains(column("attributes_bool"), name). This will generate the correct mapContains() function in the ClickHouse query, which is designed to work with Map data types.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: snuba/web/rpc/v1/trace_item_attribute_values.py#L64-L66

Potential issue: The code uses `f.has(column("attributes_bool"), name)` to query a map
column. However, the query processor `HashMapHasFunctionTransformer` is not configured
to handle the `attributes_bool` column. As a result, the function call is passed
directly to ClickHouse as `has(attributes_bool, 'attribute_name')`. The ClickHouse
`has()` function is designed for arrays, not maps. The correct function for checking key
existence in a map is `mapContains()`. This will cause a runtime type error in
ClickHouse whenever a query for a boolean attribute is executed, breaking the feature.