FTS: Collections: Deleting one collection in multi-collection index deletes the index

Build: 7.0.0-7302

Create a index with multi-collection
Drop one of the collection

Deletes the whole index itself

We know that from "Higher Level FTS Collection Requirements", this is sort of design. But still we think, this is sort of bad experience for the user. so raising this issue to have a discussion.

Not sure if this is going to be real world usecase, but here is the thinking
if customer has 10 teams, and creates a fts index with collections belonging to each team and one of the team decides to drop their collection, the whole index is deleted affecting all the other teams.

The w/a may be, rebuild the index without the collection which is going to be dropped before dropping or disable collection in the index before dropping.

But these involves, rebuilding the index.