x-pack plugins code should be organized around search, observe, protect

[shahzad31]

Describe the feature:

We have so many plugins now in x-pack/plugins there are more than 60 plugins , it will be probably helpful for developers if we can create categorisation inside plugin folder.

Describe a specific use case for the feature:

I think few advantages it can have is that it will be easier to explore around code. IDE might work well as far scroll goes. So if i am looking for some code or component from observability, it will be easier for me to find.

though downside can be that dir always create a wall inside code as well. So person working in observability may never look in any other place, but i feel like with so many pluigns, it's already hard.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[joshdover]

Great minds think alike? We are currently discussing a broader overhaul of how we structure our modules, plugins, and directories over in this issue: #71566

I think we can close this in favor of that one?

[shahzad31]

i am glad this discussion is already happening.