I think trying to create a single place for code like this to live causes more headaches than it solves. If you want to release a piece of reusable code, a special-purpose collection for that code makes more sense to me than a single collection with other unrelated code.
Among other things, this means that backwards-incompatible changes can be accommodated by bumping the collection name (e.g. community.inventory_filtering → community.inventory_filtering_v2.