Update mongo requirement from = 2.13.2 to = 2.20.0

[dependabot]

Updates the requirements on mongo to permit the latest version.

Release notes

Sourced from mongo's releases.

2.20.0

Version 2.20.0 of the Ruby driver for MongoDB is released. This adds the following new features:

• Connection strings no longer require a slash between the hosts and the options. E.g., "mongodb://example.com?w=1" and "mongodb://example.com/?w=1" are both valid connection strings now. (https://jira.mongodb.org/browse/RUBY-3329)
• Container runtime and orchestration metadata for the client environment are now sent to the server for analytics purposes. (https://jira.mongodb.org/browse/RUBY-3298)
• When connecting to a CosmosDB (Azure) or DocumentDB (Amazon) instance, a warning message will now be logged. (https://jira.mongodb.org/browse/RUBY-3296)
• When attempting a retry of a read or write operation in a sharded topology, the retry will be attempted on a different mongos instance, if possible. (https://jira.mongodb.org/browse/RUBY-2748)
• Add support for the newly-released Ruby-BSON version 5.0.
• Support for Ruby 2.5 and 2.6 has been discontinued. Support for Ruby 2.7 and JRuby 9.2 has been deprecated, and will be discontinued in a future driver version. Support for JRuby 9.4 has been added.

This release also fixes the following user-facing issues:

• The driver will now raise an error if start_transaction is invoked and the server deployment does not support transactions. (https://jira.mongodb.org/browse/RUBY-1791)
• Encountering a network error when a session is live will mark the session dirty and discard it, preventing the session from being reused when it is likely to fail. (https://jira.mongodb.org/browse/RUBY-1813)
• Tailable cursors would terminate early, after reading existing documents, instead of waiting for more. (https://jira.mongodb.org/browse/RUBY-3332)
• There was an issue where writes could fail with an exception if no session was active. (https://jira.mongodb.org/browse/RUBY-3358)

Changelog

Sourced from mongo's changelog.

.. _release-notes:

---

Release Notes

---

.. default-domain:: mongodb

This page documents significant changes in driver releases.

It is not an exhaustive list of changes and generally does not enumerate bug fixes; please consult the releases page on GitHub <https://github.com/mongodb/mongo-ruby-driver/releases>_ for a more comprehensive list of changes in each version of the driver and the releases page in Jira <https://jira.mongodb.org/projects/RUBY?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released>_ for the complete list of changes, including those internal to the driver and its test suite.

.. _release-notes-2.20:

2.20

This release includes the following new features:

• Support for Ruby 2.5 and 2.6 has been discontinued. Support for Ruby 2.7 and JRuby 9.2 has been deprecated, and will be discontinued in the next minor driver version. Support for JRuby 9.4 has been added.
• Support for the newly-released Ruby-BSON version 5.0.
• Connection strings no longer require a slash between the hosts and the options. E.g., "mongodb://example.com?w=1" and "mongodb://example.com/?w=1" are both valid connection strings now.
• Container runtime and orchestration metadata for the client environment are now sent to the server for analytics purposes.
• A warning message is now written to the log when the host is detected to be a CosmosDB (Azure) or DocumentDB (Amazon) instance.
• When attempting a retry of a read or write operation in a sharded topology, the retry will be attempted on a different mongos instance, if possible.

.. _release-notes-2.19:

2.19

This release of the Ruby driver supports MongoDB version 7.0. The Ruby driver now supports Ruby 3.2. Ruby 2.5 and 2.6 are now deprecated.

... (truncated)

Commits

• 74e4e38 RUBY-3424 Prep for 2.20 (#2852)
• 0c65ebf MONGOID-5739 Support BSON 5 (#2848)
• d332cd9 RUBY-3400 fix failing specs (#2846)
• efdaddd Use latest YARD version (#2847)
• 94eb2f5 Remove unnecessary file (#2845)
• e459c3f DOCSP-37038: Fix broken link (#2841)
• 44c607f RUBY-3399 Skip queryPlanner output specs (#2835)
• f92ecf2 RUBY-3397 update the public key for signing gems (#2834)
• 9aefc4e RUBY-3384 Update serverless tests (#2830)
• 7cb06f0 RUBY-3393: Rename BSON tutorial page (#2832)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[chef-expeditor]

Hello dependabot[bot]! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes
   a. If everything looks good, one of them will approve it, and your PR will be merged.
   b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
   c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!