Address documentation improvement suggestions from community feedback

[mariajgrimaldi]

Description

Feedback from a recent developer experience survey has highlighted several areas where the current documentation can be improved to better support developers using the Open edX platform. This issue addresses these concerns by enhancing the documentation to make it more comprehensive, accessible, and user-friendly.

The overall objective of this issue is to address all community feedback to improve the library documentation.

Tasks

Beta Give feedback

1. How to create an event from start to finish #360
   documentation +1
2. How Open edX Events work #361
   documentation +1
3. How to implement events with long term support #362
   documentation +1
4. Templates for creating new events #363
   documentation +1
5. Which events are in each named-release #364
   documentation +1
6. Where each Open edX Events is being sent #365
   documentation +1
7. Cross-repo collection of all events in the ecosystem #366
   documentation +1
8. Clarity about which events are event-bus capable and the differences between bus and non-bus events #367
   documentation +1
9. How testing is done in event-bus implementations #368
   documentation +1
10. Improve how to contribute and review expectations #369
    documentation +1
11. Include comprehensive list real life usage #370
    documentation +1
12. How to implement organization-scoped events #357
    documentation +1
13. How to implement event receivers could be clarified and possible DEPR #421
    +0