[8.13](backport #38512) [filebeat][gcs] - Cleaned up invalid CHANGELOG entry resulting from community contribution

[mergify]

Type of change

• Cleanup
• Docs

Proposed commit message

Moved bugfix CHANGELOG entry from CHANGELOG-developer.next.asciidoc to CHANGELOG.next.asciidoc

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Relates Filebeat gcs input addFiledJobs panic protection #38407

Use cases

Screenshots

Logs

---

This is an automatic backport of pull request #38512 done by [Mergify](https://mergify.com).

[botelastic]

This pull request doesn't have a Team:<team> label.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-03-21T12:18:32.202+0000

• Duration: 9 min 36 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)