feat: bump elastic-agent-libs and enable insecure defaults (backport #14956)

[mergify]

Motivation/summary

to avoid breaking changes we call SetInsecureDefaults to allow tls 1.0 and 1.1

this PR doesn't change the defaults, the method is noop for now. In a future version (where we drop insecure tls versions) this method will allow choosing tls 1.0 and 1.1, thus avoiding the breaking change in 8.x

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

Related to #10491

---

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

[kruskall]

@Mergifyio queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ test (windows-latest)

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[kruskall]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 84f9260