Advanced validation and cleaning

[CBROWN-ONS]

Description

This issue merges some of the features from TP #195
This PR will allow for a pipelined approach while cleaning and validating a GTFS.

Fixes #4,
Fixes #5,
Fixes #6,
Fixes #7,
Fixes #10,
Fixes #11,
Fixes #22,
Fixes #23,

Motivation and Context

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Test configuration details:

• OS: Windows 10
• Python version: 3.9.13
• Java version: N/A
• Python management system: MiniConda

Advice for reviewer

Checklist:

• My code follows the intended structure of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Additional comments

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

[CBROWN-ONS]

@r-leyshon Any thoughts on the failing test here?

[r-leyshon]

@CBROWN-ONS yeah I didn't get round to.sorting this. It should be simple enough. The failing test shouldn't exist any more in dev branch. I think k there's a bunch of changes in dev that should be merged to this branch and then everything will pass again hopefully.

Update - merging changes in dev removed the outdated test