Group the generated events from the AsyncAPI in some neatly organized manner.

### Use Case

In the UI view http://localhost:3000/docs under topic **Events()** the number of events is now a large list of all events produced by all In In my test situation it are already 101 events/commands

We use EventCatalog to get overview of all the events in the system, so i want to propose some kind of organization to the generated events/commands.

### Proposed Solution

Would it be an option to generate the events/command in a sub directory?

A way of organization could be:
Place the events in a directory by service name.
And maybe secondly a sub-directory of the producing channel name.
So we end up with something like:
`events\{service_a}\{channel X}\`
`events\{service_a}\{channel Y}\`
`events\{service_b}\{channel Z}\`

### Implementation Notes

_No response_

### Community Notes

* Please vote by adding a 👍 reaction to the issue to help us prioritize.
* If you are interested to work on this issue, please leave a comment.
* If this issue is labeled **needs-discussion**, it means the spec has not been finalized yet. Please reach out in the [EventCatalog Discord](https://discord.com/invite/3rjaZMmrAm).