chore: modify BatchLogProcessor method to accept max_export_size: usize parameter instead of config: &BatchConfig

[cijothomas]

No description provided.

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.5%. Comparing base (1106b0f) to head (0a37b9f).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
opentelemetry-sdk/src/logs/batch_log_processor.rs	66.6%	2 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #3119   +/-   ##
=====================================
  Coverage   80.5%   80.5%           
=====================================
  Files        126     126           
  Lines      22218   22218           
=====================================
  Hits       17889   17889           
  Misses      4329    4329           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull Request Overview

This PR refactors the BatchLogProcessor by simplifying function parameters to pass only the required max_export_batch_size value instead of the entire BatchConfig object.

Key Changes

• Modified function signature to accept max_export_size: usize parameter instead of config: &BatchConfig
• Updated all function calls to pass the specific max_export_batch_size value instead of the config object

Comments suppressed due to low confidence (1)

opentelemetry-sdk/src/logs/batch_log_processor.rs:363

• The parameter name max_export_size is inconsistent with the variable name max_export_batch_size used in the function calls. Consider renaming to max_export_batch_size for consistency.

                    max_export_size: usize,