feat: Create Python script to track usage of best practices in Mobility Database feeds #72

[cka-y]

This script runs a report to assess

• how the best practices in Add recommended presence: reconciling confusion between best practices and spec google/transit#376 are being used by the community in feeds on the Mobility Database
• if/how the practices referenced in Specify stop times shape_dist_traveled must not exceed the trip shape's maximum distance google/transit#380 and Forbid subfolders in GTFS files google/transit#379 are being used by the community in feeds on the Mobility Database
  This script will help us understand how to best make changes to the spec.

Closes #72

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Thanks for opening this pull request! You're awesome.
We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.
Examples of titles with semantic prefixes:
- fix: Fix wrong countries for some sources
- feat: Add Features and Status to MDB Schema [SOURCES]
- docs: Improvements to README.md and CONTRIBUTING.md

If your pull request includes adding or updating a source, make sure to end your pull request title with "[SOURCES]" so the GitHub workflow runs.

[davidgamez]

suggestion: Please add a documentation header to Python scripts with a brief usage description and parameters if applicable.

[qcdyx]

LGTM

[github-actions]

Congrats on getting your first pull request merged!