Add feeds section and standard-lib python script example

[Adarsh2345]

This PR resolves the missing documentation requirements highlighted in the issue. It lists the URLs for the generated RSS feeds and adds an example integration script utilizing only Python standard libraries.

Closes #84

• I commented on the issue and got the go-ahead.
• I did not edit generated files (issues/by-*, data/, site/data/, the README stats block).
• For pipeline changes, python3 -m unittest discover scripts and ruff check scripts pass.

Changes Made

Updated docs/data.md: Added a dedicated Feeds section consisting of the URLs to access the RSS feeds categorized by language, topic and the overall feed index.

Added Code Example: Provided an optimized urllib.request and json template script that downloads the compiled tracking registry, scans repository pathways for target ecosystem keywords, and prints out open items.

Verified Local Execution Output
The integration script was successfully tested locally against a running http.server module instance/
Below is the clean execution printout showing active matched tasks:

[github-actions]

Thanks @Adarsh2345, all the automated checks look good. A maintainer will review this when they can.

_{This comment is from pr-doorman, a set of plain rules the maintainers turned on. It doesn't use AI. It updates itself when you edit or push to the pull request.}

[TanbirRamim]

thanks @Adarsh2345! I pushed a cleanup: the example pointed at localhost and matched python by repo name, so it now reads the live issues.json and filters by the repo's language field (issues.json has that under repositories). Also listed where the language/topic slugs come from. Ran it, prints 86 beginner Python issues right now.

[TanbirRamim]

merged, thanks! #81 is yours now if you still want it. and if the radar's been useful to you, a star helps other newcomers find it.

[Adarsh2345]

Thanks @TanbirRamim I've added a star . In GitHub contributions is it better to avoid comments and extra exception handling in general or was this specific to this codebase?

[TanbirRamim]

thanks for the star! not a general rule. here it was a docs snippet, so shorter is easier to copy and adapt, and a try/except that just prints the error hides the traceback people need when something breaks. in real code keep comments that explain why, and catch exceptions where you can actually do something about them. just match whatever the repo already does.