In span first, we're introducing a new span filtering init option called ignore_spans which allows to ignore spans at start time based on name and attributes.

• Spans ignored this way emit a new ignored client report (set via NoOpStreamedSpan.unsampled_reason).
• If a segment matches one of the rules in ignore_spans, the whole span tree will be ignored. The implementation achieves this by allowing NoOpStreamedSpans to be set on the scope in this one single case, so that their children can easily determine their segment was dropped.
• If a segment is not ignored but one of its children spans (regardless of depth) is, ONLY that one span will be ignored, not its whole subtree.

Spec: https://develop.sentry.dev/sdk/telemetry/spans/filtering/#filter-with-ignorespans