feat: Update to latest MongoDB.Driver version

[ilmax]

Changes

The MongoDB.Driver has been updated to the latest version to allow Akka and Aspire to work well together again. This fixes an Issue introduced by the MongoDB.Driver because latest version is now strong named.

More info can be found here, the issue this change is the same as this one.

Not sure what kind version bump this change requires on the Akka side

Checklist

For significant changes, please ensure that the following have been completed (delete if not relevant):

• This change follows the Akka.NET API Compatibility Guidelines.
• This change follows the Akka.NET Wire Compatibility Guidelines.
• I have reviewed my own pull request.
• Design discussion issue #
• Changes in public API reviewed, if any.
• I have added website documentation for this feature.

[ilmax]

@Aaronontheweb any chance we can bump to latest MongoDB Driver? That would allow using Akka.Persistence.MongoDb with the 8.2 version of Aspire.MongoDB.Driver (and also to whoever updated the mongodb driver to latest)

[Aaronontheweb]

@Aaronontheweb any chance we can bump to latest MongoDB Driver? That would allow using Akka.Persistence.MongoDb with the 8.2 version of Aspire.MongoDB.Driver (and also to whoever updated the mongodb driver to latest)

Yep, fine with me

[Aaronontheweb]

So wait a minute, is @ilmax the new version of this driver strong-named?

[ilmax]

@Aaronontheweb yes it is, that's why this Akka update is required, otherwise I could simply reference the latest mongodb.driver and be good to go.
Essentially the mongo people made a breaking change in this latest version 🤷‍♂️

[Aaronontheweb]

sigh, this is probably going to create problems for other users but I guess that's inevitable unless they plan on never upgrading their Mongo drivers

[ilmax]

Yeah, I wanted to write something about versioning, but I have no idea what's the right thing to do here. If the user has no other dependency that use mongo, it's all good, if there's another dependency that references the old mongo driver, this is a problem.