Add persistence acknowledgement support for shipper

[rdner]

What does this PR do?

Now the shipper output is able to receive acknowledgement of the
persisted events from the shipper server.

Also, added the UUID verification in case the client is reconnected to
a different server.

Why is it important?

To avoid data loss.

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.

Related issues

• Closes Make the shipper output to acknowledge batches based on PersistedIndex not AcceptedCount #32329

[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: 2022-08-22T15:12:09.511+0000

• Duration: 126 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22656
Skipped	1937
Total	24593

💚 Flaky test report

Tests succeeded.

🤖 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!)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @rdner? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)
  To fixup this pull request, you need to add the backport labels for the needed
  branches, such as:
• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[rdner]

E2E test failure is not related to the change:

[2022-08-16T17:23:54.410Z] time="2022-08-16T17:23:52Z" level=fatal msg="could not add package to policy; API status code = 400; response body = {"statusCode":400,"error":"Bad Request","message":"Package policy is invalid: inputs.logfile.streams.system.auth.vars.preserve_original_event: Preserve original event is required\ninputs.logfile.streams.system.auth.vars.tags: Tags is required"}"

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[cmacknz]

Mostly looks good. I think we'll need a way to benchmark throughput between a beat and the shipper to really know how well this performs.