feat(meta): Add record_meta field to counters consumer

[evanh]

This field will be used by the materialized view to determine whether the row
should be processed into the meta table.

Depends on #5681

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.93%. Comparing base (f5f9208) to head (9a6b53d).

✅ All tests successful. No failed tests found ☺️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5680   +/-   ##
=======================================
  Coverage   89.92%   89.93%           
=======================================
  Files         898      898           
  Lines       43453    43453           
  Branches      299      299           
=======================================
+ Hits        39077    39078    +1     
+ Misses       4334     4333    -1     
  Partials       42       42           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nikhars]

Since this is an optimization, would it be better to do it via an allowlist rather than a blacklist? That way we avoid new use cases being recorded in the meta table by default. Something like escalating issues causing unnecessary overhead on the meta table.

[evanh]

Since this is an optimization, would it be better to do it via an allowlist rather than a blacklist?

I did it this way so that we can avoid a potential step in someone creating a new use case. This way, if a product person creates a new use case, they don't then have to take another step to get auto-complete, it just comes for free.