Upgrade mongodb-client to 5.1.3

[gcw-it]

The extension compiles now, and the integration test runs successfully.

The following changes were necessary:

• changed/removed access to deprecated and removed classes/methods
• adjusted graalvm substitutions

There were a couple of deprecations, that were ignored for too long and the corresponding classes/methods were removed in this or an earlier version of the mongoldb java client.

I believe there is still some work to do with the extension, because there are still more than 30 deprecation warnings during compilation.

[gsmet]

Awesome, thanks!

I added some small questions inline.

BTW, if you feel like it and things are relatively straightforward, I'm all for removing the calls to deprecated methods.
It might be too involved though so feel free to not do it.
Probably a good idea to do it in a specific commit if you pursue this.

[gsmet]

Should we also drop the field/method in our class?

It doesn't have any replacement that we would need to support?

[gcw-it]

Thanks for your attentiveness, yes we should drop the field. I'll take care of it.

According to the 4.11.1 Javadocs this option isn't supported on a database level from MongoDB 4.4 onwards.

No additional options were introduced between the versions.

[gsmet]

There are no replacement or additional fields we need to support?

[gcw-it]

According to the 4.11.1 Javadocs these two options aren't supported on a database level from MongoDB 4.4 onwards.

In comparison to 4.11.1 only those two fields were removed and none were added.

[gcw-it]

I believe there will be more work that needs to be invested in this area in the future.
The whole Map-Reduce functionality was deprecated in version 5.0 and should be replaced with aggregates.
See Map-Reduce.

[gcw-it]

removed the superfluous field.

[gsmet]

Sorry to be that guy but could you have a first line in the commit message saying it's the upgrade? (i.e. the title of the PR)

[gcw-it]

No problem.

[gsmet]

Perfect. In general, no problem to add a lot more details to the message but the first line should be really the top level thing we are doing.

[gsmet]

Thanks! Let's run CI and see how it goes.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 03e64b3.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging/deployment

✖ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

• Expecting actual: ["-6","-7","-8","-10","-11","-12","-13","-14"] to start with: ["-6", "-7", "-8", "-9"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-6","-7","-8","-10","-11","-12","-13","-14"]
to start with:
  ["-6", "-7", "-8", "-9"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:41)