ref(profiling): emit (processed) profile outcomes in profiling consumers

[viglia]

This closes issue https://github.com/getsentry/team-ingest/issues/563

[codecov]

Codecov Report

Attention: Patch coverage is 36.66667% with 19 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/profiles/task.py	28.00%	18 Missing ⚠️
src/sentry/ingest/billing_metrics_consumer.py	75.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #80189      +/-   ##
==========================================
- Coverage   78.09%   78.08%   -0.01%     
==========================================
  Files        7178     7176       -2     
  Lines      317128   317142      +14     
  Branches    43719    43722       +3     
==========================================
+ Hits       247649   247651       +2     
+ Misses      63136    63135       -1     
- Partials     6343     6356      +13     

[Dav1dde]

process_profile_task has a lot of code paths that exit/return without emitting an outcome, all of these cases now would never emit an outcome, I don't think this is desired, I assume that these at least should be counted in some error category.

[viglia]

process_profile_task has a lot of code paths that exit/return without emitting an outcome, all of these cases now would never emit an outcome, I don't think this is desired, I assume that these at least should be counted in some error category.

@Dav1dde as we discussed quickly over slack, all the early return are taken care of (inside the functions body when we catch the exception).

The only place where we return early and not emit an outcome is here at the very beginning where we assert profile is not None.
If that fails, i.e. profile is None, then I couldn't even distinguish between a profile and a chunk, so I'm not sure which outcome should be emitted in that case.