Update app name in docs (add TRANSIT-data-tools)

[ghost]

Checklist

• Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
• Any modified or new methods or classes have helpful JSDoc and code is thoroughly commented
• The description lists all applicable issues this PR seeks to resolve
• The description lists any configuration setting(s) that differ from the default settings
• All tests and CI builds passing
• The description lists all relevant PRs included in this release (remove this if not merging to master)
• e2e tests are all passing (remove this if not merging to master)
• Code coverage does not significantly worsen (ideally it improves) (remove this if not merging to master)

Description

Please explain the changes you made here and, if not immediately obvious from the code, how they resolve any referenced issues (and PRs if merging to master). Be sure to include all issues being resolved and any special configuration settings that are need for the software to run properly with these changes.

[landonreed]

@ritesh-warade-ibigroup, I'm going to change your base branch to dev. FYI, all PRs should typically be made to dev (after a few stack up, we generally make a PR from dev to master).