ref(spans): Split off span description scrubbing into separate file (#…

…2303)

Move all span description scrubbing logic into a separate file. This
should make it easier to contribute, and prepares for the next step:
Moving span tagging from metrics extraction to normalization.

Changes in `relay-general/src/store/`:

```
transactions/processor.rs -> normalize/span/description.rs  (only span-specific parts)
normalize/spans.rs        -> normalize/span/attributes.rs
```

This PR contains no functional changes.

.gitignore

@@ -1,6 +1,7 @@
 # Rust
 **/*.rs.bk
 target
+*.pending-snap
 
 # Python
 .venv/

relay-general/src/store/normalize.rs

@@ -30,15 +30,15 @@ use crate::types::{
 use crate::user_agent::RawUserAgentInfo;
 
 pub mod breakdowns;
+pub mod span;
+pub mod user_agent;
+
 mod contexts;
 mod logentry;
 mod mechanism;
 mod request;
-mod spans;
 mod stacktrace;
 
-pub mod user_agent;
-
 /// Defines a builtin measurement.
 #[derive(Debug, Default, Clone, Serialize, Deserialize)]
 #[serde(default, rename_all = "camelCase")]
@@ -198,7 +198,7 @@ impl<'a> NormalizeProcessor<'a> {
 
  fn normalize_spans(&self, event: &mut Event) {
  if event.ty.value() == Some(&EventType::Transaction) {
- spans::normalize_spans(event, &self.config.span_attributes);
+ span::attributes::normalize_spans(event, &self.config.span_attributes);
  }
  }
 
@@ -841,7 +841,10 @@ pub fn light_normalize_event(
  // transactions don't have many spans, but if this is no longer the
  // case and we roll this flag out for most projects, we may want to
  // reconsider this approach.
- spans::normalize_spans(event, &BTreeSet::from([SpanAttribute::ExclusiveTime]));
+ span::attributes::normalize_spans(
+ event,
+ &BTreeSet::from([SpanAttribute::ExclusiveTime]),
+ );
  }
 
  Ok(())