update MongoDB.Driver PackageReference to 3.3

[badge2033]

update MongoDB.Driver PackageReference to 3.3
in this version package MongoDB.Driver.Core was merged with the main package and so was removed

[cla-checker-service]

💚 CLA has been signed

[github-actions]

👋 @badge2033 Thanks a lot for your contribution!

It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it.

Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.

[badge2033]

fixes issue #2504

[codewithmecoder]

Please help review and release on this merge on this as I am stack with the version conflict and cannot update MongoDB.Driver to version 3+.

Thank you.

[stevejgordon]

We need to consider this one a bit more. The issue is, for consumers using older packages, this may cause conflicts and breaking changes, which we need to manually test and validate.

[badge2033]

We need to consider this one a bit more. The issue is, for consumers using older packages, this may cause conflicts and breaking changes, which we need to manually test and validate.

i think this reasoning -while valid- is counter productive.
multiple projects are locked from a needed update for the mongo packages because of the desynchronised dependencies on the elastic packages.
But conservative project managers who are not keen on speedy updating, will stay on elastic old packages version, so they won't be affected either way.
please reconsider this update as very urgent.