[EXPORTER] Fix crash in ElasticsearchLogRecordExporter

[ShadowMaxLeb]

Fixes #3078

Using constructor with user provided options in ElasticsearchLogRecordExporter was making the program crash due to synchronization_data_ not being intialized when built with async behavior (-DWITH_ASYNC_EXPORT_PREVIEW=ON)

Changes

Constructors have been changed so the default one always calls the one with options as parameters to ensure to always initialize everything.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ShadowMaxLeb / name: Maxime Leblanc (b1cf143, d010ced)

[netlify]

✅ Deploy Preview for opentelemetry-cpp-api-docs canceled.

Name	Link
🔨 Latest commit	d010ced
🔍 Latest deploy log	https://app.netlify.com/sites/opentelemetry-cpp-api-docs/deploys/6704c13624708500081783ea

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.82%. Comparing base (497eaf4) to head (d010ced).
Report is 137 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3082      +/-   ##
==========================================
+ Coverage   87.12%   87.82%   +0.71%     
==========================================
  Files         200      195       -5     
  Lines        6109     5968     -141     
==========================================
- Hits         5322     5241      -81     
+ Misses        787      727      -60     

see 125 files with indirect coverage changes

[marcalff]

Thanks @ShadowMaxLeb for the patch.

Please sign the contributor agreement (CLA), so this PR can be merged to the main branch.
The CLA will apply to all PR, present and future, so it only needs to be done once.

[marcalff]

LGTM, thanks for the fix.

[marcalff]

@ShadowMaxLeb

Thanks for the contribution.

This PR is approved and ready to be merged to the main branch.
Unfortunately, we (opentelemetry-cpp maintainers) do not have github permissions to update this branch.
This is needed to:

• perform a main -> PR merge first, to align the PR branch to main
• perform the PR -> main merge, to accept the contribution.

Please allow maintainers to make edits (there is a checkbox in the github UI for that), or perform a main -> PR merge so we can take it.

Thanks.

[marcalff]

Added the merge conflict tag.
There are no merge conflicts, only the down merge needs to be resolved:

This branch is out-of-date with the base branch

[ShadowMaxLeb]

Since the fork ispart of an organization, it seems that I do not have the possibility to allow maintainers (https://github.com/orgs/community/discussions/5634).

I will update the PR.