build(deps): bump go.mongodb.org/mongo-driver from 1.17.4 to 1.17.6

[dependabot]

Bumps go.mongodb.org/mongo-driver from 1.17.4 to 1.17.6.

Release notes

Sourced from go.mongodb.org/mongo-driver's releases.

MongoDB Go Driver 1.17.6

The MongoDB Go Driver Team is pleased to release version 1.17.6 of the official MongoDB Go Driver.

[!NOTE] Due to a bug in the Go Driver release automation, there is no 1.17.5 release.

Release Highlights

This release makes various maintainability improvements to the Go Driver development and release automation.

What's Changed

📝 Other Changes

• GODRIVER-3560 Use lambda-specific arn for FaaS by @​prestonvasquez in mongodb/mongo-go-driver#2093
• Use a pinned Go version for golangci-lint. by @​matthewdale in mongodb/mongo-go-driver#2151
• Disable merge-up from release/1.17 by @​alcaeus in mongodb/mongo-go-driver#2202

Full Changelog: mongodb/mongo-go-driver@v1.17.4...v1.17.6

For a full list of tickets included in this release, please see the list of fixed issues.

Documentation for the Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. For issues with, questions about, or feedback for the Go Driver, please look into our support channels, including StackOverflow. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go Driver is greatly appreciated!

Commits

• d2fa0ab BUMP v1.17.6
• f1d540b BUMP v1.17.5
• b879028 GODRIVER-3654 Don't test v1 branches against latest server. (#2188)
• 21f47d4 Allow ignore-for-release label to satisfy label checker (#2203)
• 8708ca8 Disable merge-up from release/1.17 (#2202)
• 0b2794f GODRIVER-3612 Add an internal-only NewSessionWithLSID API (v1) (#2183)
• 747a8d0 Consider HTTP 429 a succcessful response in the Markdown link check. (#2191)
• 8c336ff Pin drivers-evergreen-tools to rev 98f6b0e in v1. (#2184)
• 106cff3 Retry Markdown link checks on HTTP 429 (v1) (#2186)
• d406474 GODRIVER-3564: Add config and workflows for release note labels (#2148)
• 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)

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : 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 @dependabot[bot]? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.