Currently, there are many tests skipping the suites that implicitly create sharded collections (like this one) just because they are checking if the collection exists after a drop.
These tests fail in this kind of suite because we implicitly recreate the collection on a drop to make sure it is a sharded collection.

The tests with the described behavior are tagged with assumes_no_implicit_collection_creation_after_drop.

The aim is to eventually enable the tests that are not running on those suites that implicitly create sharded collections just because they are checking if the collection exists after a drop.