Add collectionName and databaseName attributes to MongoDbProvider

[vy]

This work is a clone of #3322 authored by @jesmith17. Commit signatures were missing, Spotless was failing, and author could not address these issues. I created a separate PR to avoid truncating the git & GitHub conversation history in the old PR.

[ppkarwasz]

Looks good, thanks for fixing #3322!

Just a quick note on the tests in the log4j-mongodb module:

• The newly added integration tests (CollectionNameIT, DatabaseAndCollectionNameIT, and NoDatabaseAndCollectionNameIT) seem somewhat redundant. From what I can tell, the existing ProviderTest unit test already verifies that the correct strings are passed to the MongoDB driver, so these ITs might not add much value beyond that.
• Not directly related to this PR, but something we might want to track: the CappedIntIT and CappedLongIT tests don’t appear to actually verify that the collection created is capped. It could be worth opening an issue to address that.

When I get a chance, I’ll try porting this PR over to the 2.x branch. After that, maybe we can switch roles—I'll open the PR, and you can do the honors of reviewing. 😉

[vy]

@ppkarwasz, removed CollectionNameIT and DatabaseAndCollectionNameIT. (I couldn't understand what you meant with NoDatabaseAndCollectionNameIT.)

[ppkarwasz]

I couldn't understand what you meant with NoDatabaseAndCollectionNameIT.

I think I was mistakenly looking at the 2.x branch: https://github.com/apache/logging-log4j2/tree/2.x/log4j-mongodb/src/test/java/org/apache/logging/log4j/mongodb

BTW: regarding 2.x you already introduced this change several months ago: #3467. I don't know why I did add this PR to milestone 2.25.0.

[vy]

regarding 2.x you already introduced this change several months ago: #3467. I don't know why I did add this PR to milestone 2.25.0.

Doh! Never occurred to me either! 🤦‍♂️ I guess we are both experiencing "burnout as a life style"? 😅