docs(data_classes): improve Event Source Data Classes documentation

[anafalcao]

Issue number:
#1163

Summary

This PR enhances the Event Source Data Classes documentation by adding copy-and-paste examples, including event examples for all event sources, updating the header explanation, revising the Getting Started section, and adding explanations to data sources that previously lacked them.

Changes

• Added copy-and-paste code examples for each event source data class
• Included sample event JSON for all event sources
• Updated the header explanation to provide a clearer overview of event source data classes
• Revised the getting started section to make it more user-friendly
• Added explanations to data sources that were missing them

User experience

Before:

• Users had to manually construct event handling code
• Limited examples and no sample event JSONs were provided
• Some data sources lacked explanations, making it difficult for users to understand their purpose

After:

• Users can copy and paste ready-to-use code examples for quick implementation
• Sample event JSONs are provided, allowing users to understand the structure of incoming events
• Comprehensive explanations for all data sources help users choose the appropriate event source for their use case
• Improved getting started section guides users through the implementation process more effectively

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.22%. Comparing base (5517f1d) to head (69ed199).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #5916   +/-   ##
========================================
  Coverage    96.22%   96.22%           
========================================
  Files          233      233           
  Lines        10965    10965           
  Branches       790      790           
========================================
  Hits         10551    10551           
  Misses         327      327           
  Partials        87       87           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[leandrodamascena]

AMAZING WORK @anafalcao! APPROVED!