Plugins of plugins

[MartyMcFlyInTheSky]

Would it make sense to have a mechanism in lazy.nvim that would allow a plugin to easily manage its plugins also via lazy.nvim? This would put the user in control while at the same time fostering the notion of having plugins with child plugins, so it's easier to see dependencies. Also lazy.nvim could establish a standardized ways to deal with plugin-plugins which can then be expected from any plugin, allowing for easier code navigation. I'm thinking about the telescope extensions here, but there are certainly other usecases (e.g. a general testing framework, allowing for pytest, ctest, etc.. extensions).

The design would need to be carefully thought out with the foresight that maybe a general enough plugin might be merged into nvim master at some point in which case the plugin's plugin would move one layer down, now becoming regular plugins. What's your take on the idea?