Tests over API Best Practices

[colin99d]

Description

I know this isn't supposed to be until next sprint, but I had nothing else to do. Adds a super cool function that crawls our API and makes sure no parameter names are probably incorrect versions of standard parameter names. It's also super verbose to make fixing EZ. @minhhoang1023, let me know if there are common mistakes I need to add to the dictionary

• need to ensure it checks ALL functions (switch to Auto Generate API Documentation #2360 method of getting functions)
• Wait for virtual path to be merged and then just read that

Update: This PR found a LOT of places where we missed stuff (over 90). This will take me a decent amount of time to be ready.

I finished changing all of the bad functions. I am now trying to add a reliable way to check all of them. To do this I have added CI checks over our jupyter notebooks.

How has this been tested?

Ran pytest, add pytest coverage over jupyter notebooks.

Checklist:

• Update our Hugo documentation following these guidelines.
• Update our tests following these guidelines.
• Make sure you are following our CONTRIBUTING guidelines.
• If a feature was added make sure to add it to the corresponding scripts file.

Others

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My code passes all the checks pylint, flake8, black, ... To speed up development you should run pre-commit install.
• New and existing unit tests pass locally with my changes. You can test this locally using pytest tests/....