[8.x](backport #42690) build(deps): bump github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.7.0 to 1.8.2

[mergify]

Bumps github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.7.0 to 1.8.2.

Release notes

Sourced from github.com/Azure/azure-sdk-for-go/sdk/azidentity's releases.

sdk/azidentity/v1.8.2

1.8.2 (2025-02-12)

Other Changes

• Upgraded dependencies

sdk/azidentity/v1.8.1

1.8.1 (2025-01-15)

Bugs Fixed

• User credential types inconsistently log access token scopes
• DefaultAzureCredential skips managed identity in Azure Container Instances
• Credentials having optional tenant IDs such as AzureCLICredential and InteractiveBrowserCredential require setting AdditionallyAllowedTenants when used with some clients

Other Changes

• ChainedTokenCredential and DefaultAzureCredential continue to their next credential after ManagedIdentityCredential receives an unexpected response from IMDS, indicating the response is from something else such as a proxy

sdk/messaging/azservicebus/v1.8.0

1.8.0 (2025-02-11)

Features Added

• ServiceBusClient allows the endpoint to be overridden with ServiceBusClientOptions.CustomEndpoint, to use TCP proxies with AMQP. (PR#23843)

sdk/messaging/azservicebus/v1.8.0-beta.2

1.8.0-beta.2 (2025-01-14)

Features Added

• ServiceBusClient allows the endpoint to be overridden with ServiceBusClientOptions.CustomEndpoint, to use TCP proxies with AMQP. (PR #23843)

Bugs Fixed

• Receivers had a bug where a message could be received but not returned to the user. Callers would see that, occasionally, a message would not be returned from ReceiveMessages(), but would appear to have been received. Thanks to @​patrickwhite256 for reporting this issue. (PR #23929)

sdk/messaging/azservicebus/v1.7.4

1.7.4 (2025-01-13)

Bugs Fixed

• Receivers had a bug where a message could be received but not returned to the user. Callers would see that, occasionally, a message would not be returned from ReceiveMessages(), but would appear to have been received. Thanks to @​patrickwhite256 for reporting this issue. (PR #23929)

sdk/messaging/azservicebus/v1.7.3

1.7.3 (2024-10-14)

Bugs Fixed

... (truncated)

Commits

• 5474626 Prepare azidentity v1.8.2 for release (#24108)
• 4d55b0c [tracing/azotel] Enable span link and propagation support (#24081)
• dc2f507 Increment package version after release of storage/azdatalake (#24105)
• 7efafe4 Increment package version after release of storage/azfile (#24101)
• ae43d8b Increment package version after release of storage/azblob (#24102)
• 03b82ac prep for azdatalake preview (#24103)
• 6ee011a [Storage] Prep for release stg97 - Blob and Files (#24100)
• db0a6cb [Storage] stg97 features (#24080)
• d9d7f1b Support Linux environment (#24095)
• 57bab21 Parameterize test-pipeline version separator (#24094)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

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

[mergify]

Cherry-pick of 02c934b has failed:

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

You are currently cherry-picking commit 02c934be7.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum

no changes added to commit (use "git add" and/or "git commit -a")

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

[elasticmachine]

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

[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-42690 upstream/mergify/bp/8.x/pr-42690
git merge upstream/8.x
git push upstream mergify/bp/8.x/pr-42690

[botelastic]

Hi!
We just realized that we haven't looked into this PR in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[botelastic]

Hi!
This PR has been stale for a while and we're going to close it as part of our cleanup procedure.
We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team.
Feel free to re-open this PR if you think it should stay open and is worth rebasing.
Thank you for your contribution!