[elramen]

Make cogs measurements more granular by using the cogs future wrapper at a lower level in the call stack.

If we want even more granularization, and the ability to measure things that happen in the middle of a request's processing (i.e. nested cogs futures), we can do the following:

• Use a thread-local pointing to the currently polling cogs-future's "tracker" (when a request's tokio task gets the thread, the top level cogs future sets the thread-local to point to its tracker).
• The tracker stores total: cpu time elapsed in the request (as last recorded; only updated when a future finishes).
• When a cogs future starts, it copies total into a local variable before.
• When a cogs future polls, it increases its local cpu time: gross_local. It is gross because it includes nested futures.
• When a cogs future finishes, it updates a map in the tracker that contains elapsed time per category, calculated by: category += gross_local - (total - before) where total - before make up nested cogs futures' elapsed time.
• When a cogs future finishes, it also updates the tracker's total = before + gross_local.

This is a bigger change and it isn't prioritized atm, but something to keep in mind for the future in case we need it.

Fixes: https://linear.app/getsentry/issue/INGEST-1289