Serialize cronjob doc and remove type property

[asteriscos]

Description

Hi team,
this PR fixes the statistics cronjob request body to fix the "mapper_parsing_exception". It seems the opensearch dependency that executes the bulk doc insert has changed.

https://github.com/opensearch-project/OpenSearch-Dashboards/blob/1.2.0/package.json#L121
https://github.com/opensearch-project/OpenSearch-Dashboards/blob/2.4.1/package.json#L133

Issues Resolved

Closes https://github.com/wazuh/wazuh-automation/issues/1020

Evidence

Discover

Statistics

Test

• Verify the Statistics information is indexed in Cluster mode ON and OFF

Cluster Mode ON	Cluster Mode OFF
⚫	⚫

Check List

• All tests pass
  • yarn test:jest
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[Desvelao]

review:

code 🟢

Wazuh dashboard

Legend:
⚫: none
🟢: passed
🔴: failed
🟡: warning
⚪: not applicable

Environment:
Platform: Wazuh dashboard

Test	Chrome	Firefox	Safari
Verify the Statistics information is indexed in Cluster mode	🟢	🟢	⚫
Verify the Statistics information is indexed in Manager mode	🟢	🟢	⚫

Details

🟢 Verify the Statistics information is indexed in Cluster mode

Chrome - 🟢

Firefox - 🟢

Safari - ⚫

🟢 Verify the Statistics information is indexed in Manager mode

Chrome - 🟢

Firefox - 🟢

Safari - ⚫

[github-actions]

Code coverage (Jest)	%	values
Statements	8.76%	( 3236 / 36906 )
Branches	4.5%	( 1291 / 28670 )
Functions	7.63%	( 698 / 9142 )
Lines	8.83%	( 3121 / 35340 )

[chantal-kelm]

review:

code 🟢

Wazuh dashboard

Legend:
⚫: none
🟢: passed
🔴: failed
🟡: warning
⚪: not applicable

Environment:
Platform: Wazuh dashboard

Test	Chrome	Firefox	Safari
Verify the Statistics information is indexed in Cluster mode	🟢	🟢	🟢
Verify the Statistics information is indexed in Manager mode	🟢	🟢	🟢

Details

🟢 Cluster mode OFF

Chrome - 🟢

Firefox - 🟢

Safari - 🟢

🟢 Cluster mode ON

Chrome - 🟢

Firefox - 🟢

Safari - 🟢

[github-actions]

The backport to 4.4-7.16 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.16 4.4-7.16
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.16
# Create a new branch
git switch --create backport-5150-to-4.4-7.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6a6ea1f8af52fa63b30a39fb7589ccf4847e71b3
# Push it to GitHub
git push --set-upstream origin backport-5150-to-4.4-7.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.16

Then, create a pull request where the base branch is 4.4-7.16 and the compare/head branch is backport-5150-to-4.4-7.16.

[github-actions]

The backport to 4.4-7.10 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.10 4.4-7.10
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.10
# Create a new branch
git switch --create backport-5150-to-4.4-7.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6a6ea1f8af52fa63b30a39fb7589ccf4847e71b3
# Push it to GitHub
git push --set-upstream origin backport-5150-to-4.4-7.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.10

Then, create a pull request where the base branch is 4.4-7.10 and the compare/head branch is backport-5150-to-4.4-7.10.