fix: Move batch processor to 100klrps scenario and add otap-batch-otap

[JakeDern]

Change Summary

This PR moves the continuous batch processor benchmarks to the 1ooklrps scenario and adds an otap-batch-otap configuration.

I think the batch processor benchmarks were mistakenly added to the "passthrough" scenario which states it's for scenarios with no processor in the middle. The dashboard also does not seem to be set up properly for these and we want to add otap-batch-otap as mentioned here: #2246 (comment)

• Closes Batch processor continuous benchmarks #2277

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.00%. Comparing base (a88939a) to head (821556f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2395      +/-   ##
==========================================
- Coverage   88.01%   88.00%   -0.02%     
==========================================
  Files         582      582              
  Lines      204179   204179              
==========================================
- Hits       179713   179688      -25     
- Misses      23940    23965      +25     
  Partials      526      526              

Components	Coverage Δ
otap-dataflow	90.05% <ø> (-0.02%)	⬇️
query_abstraction	80.61% <ø> (ø)
query_engine	90.61% <ø> (ø)
syslog_cef_receivers	∅ <ø> (∅)
otel-arrow-go	52.44% <ø> (ø)
quiver	91.91% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JakeDern]

CC: @cijothomas

[cijothomas]

LGTM.
(Regarding using batch processor in passthrough - I will come back on it, if needed later. They can be truly passthrough now without any processor in the middle.)