[8.x](backport #5720) Update all inconsistent OTel dependencies to v0.110.0

[mergify]

There were some dependencies that dependabot missed updating due to failures in dependabot runs (example: https://github.com/elastic/elastic-agent/actions/runs/11153122424/job/31000038669). This is causing all future runs to fail as well. This PR attempts to fix the current branch so that future dependabot PRs are correctly updated.

---

This is an automatic backport of pull request #5720 done by Mergify.

[mergify]

Cherry-pick of bfef4fa has failed:

On branch mergify/bp/8.x/pr-5720
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit bfef4fa0a1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	both modified:   internal/pkg/otel/README.md

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[lahsivjar]

I noticed that the mergify bot added the backport label back after I removed it - this should not be required for the 8.x branch since it is still on v0.109 of the collector.

This is not correct, all PRs have to go to 8.x branch.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.x/pr-5720 upstream/mergify/bp/8.x/pr-5720
git merge upstream/8.x
git push upstream mergify/bp/8.x/pr-5720

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube