feat: Emit breakdowns for all transactions

[dashed]

Begin emitting breakdowns for all transactions. The performance-ops-breakdown will instead be used to gate the UI product features for displaying these breakdowns.

Related PR: getsentry/relay#993

[k-fish]

👍

[dashed]

@untitaker It seems like we have these assertions in the Relay project options tests (and in other places):

sentry/tests/sentry/api/endpoints/test_relay_projectconfigs_v2.py

Lines 107 to 109 in cbd0e17

	# Sweeping assertion that we do not have any snake_case in that config.
	# Might need refining.
	assert not {x for x in _get_all_keys(result) if "-" in x or "_" in x}

And enabling the breakdowns project options is failing these assertions.

The project options are as follows:

{
   "breakdowns":{
      "span_ops":{
         "matches":[
            "http",
            "db",
            "browser",
            "resource"
         ],
         "type":"span_operations"
      }
   }
}

Can you advise if the dictionary keys should not contain hyphens or underscores?

[untitaker]

@dashed we used to have a bug where we accidentally returned snakecase for all options in Sentry even though they were encoded as camelCase in Relay. If it is possible I would make every key/literal/constant/symbol in project config camelCase for consistency.

Just took a quick look around the code, so I hope the following makes sense. I would:

1. change the type value to camelCase: https://github.com/getsentry/relay/blob/e3c064e213281c36bde5d2b6f3032c6d36e22520/relay-general/src/store/normalize/breakdowns.rs#L205
2. modify the assertion such that span_ops specifically is exempted from those checks, as it seems that this is passed through into the event (I'd say event schema is more important to keep internally consistent)

[untitaker]

getsentry/relay#993 (comment)

[dashed]

@untitaker I'm going to rename this to camel case for the project options.

[untitaker]

Please absolutely make sure to merge the Relay PR and deploy it first.

[dashed]

/gcbrun