feat(event-normalization): Update is_ai_span and infer_ai_operation_type to use gen_ai.operation.name

[constantinius]

The gen_ai.operation.name should be used in preference over span.op in order to determine whether a span is an AI span.

Closes https://linear.app/getsentry/issue/TET-1525/update-relay-logic-to-use-gen-aioperationname

[linear]

TET-1525 Update relay logic to use `gen_ai.operation.name`

[constantinius]

This should be merged and deployed after getsentry/sentry#104242 is deployed, otherwise we would get wrong ai_client values for gen_ai.operation.type attributes since we would go to the catch-all clause.

[constantinius]

Okay, the dependent commit in Sentry seems deployed now, this is good to go.

[Dav1dde]

Can be simplified to:

    let op_type = data
        .gen_ai_operation_name
        .value()
        .or(span.op.value())
        .and_then(|op| operation_type_map.get_operation_type(op));

    if let Some(operation_type) = op_type {
        data.gen_ai_operation_type
            .set_value(Some(operation_type.to_owned()));
    }

Also this is potentially a bug, it overwrites an existing type. If any SDK were to set this, it will be deleted. Generally we take the approach in Relay not to mess with existing data and only add data.

[constantinius]

The potential bug is unrelated, but as far as I know this was intentional. I'll discuss with @vgrozdanic.

[vgrozdanic]

This was made by design, because this is not intended to be set by SDK.

We want to control this mapping, and not commit to doing this in SDKs because this is partially based on OTEL spec which is still in development phase and not yet stable