DOC: New documentation of PySherlock

[ansnfernand]

Description

New documentation of PySherlock with examples.

Checklist:

• Run unit tests and make sure they all pass
  - Run tests without Sherlock running
  - Run tests with Sherlock GRPC connection
• Check and fix style errors
  - pre-commit command line check
  - Problems tab in PyCharm
• [] Bench test new/modified APIs by using and modifying the code in the example for the API method
• Add new classes to rst files, located at: \doc\source\api
• Generate documentation
• Verify the HTML. It gets generated at: \doc\build\html.
  - Open index.html
  - Click on "API Reference" at the top.
  - Verify HTML for API changes.
• Check that test code coverage is at least 80% when Sherlock is running
• Make sure that the title of the pull request follows Commit naming conventions (e.g. feat: adding new PySherlock command)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.25%. Comparing base (2a61d77) to head (472e271).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #480      +/-   ##
==========================================
+ Coverage   60.22%   60.25%   +0.02%     
==========================================
  Files          23       23              
  Lines        4983     5032      +49     
==========================================
+ Hits         3001     3032      +31     
- Misses       1982     2000      +18     

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