Fix BigQuery API (and others) not showing in Parsons Documentation

[bmos]

#1721 broke our documentation build, which needs access to all our dependencies.

What is this change?

• Install parsons with all extras during build job of documentation workflow
• Improve type hints
• Improve docstrings
• Remove unused variables
• Pass **load_kwargs to load_table_from_file() as described in docstring
• Mark static methods with @staticmethod

How to test the changes (if needed)

• CI tests should be adequate

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?

• label: Breaking change — This PR introduces one or more breaking changes.
• label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
parsons/google
google_bigquery.py					67, 902, 980, 1779-1784, 1793-1818
Project Total

This report was generated by python-coverage-comment-action

[shaunagm]

@bmos can you confirm this should be a non-breaking change?

[bmos]

I changed the names of functions that are not intended for public use. It would be breaking if someone was using those utility functions. If desired, I can add deprecation aliases to make it 100% not breaking even in that edge case.

[shaunagm]

Yes please - or separate them out into two PRs so we can fix the broken docs quickly and wait until the next major release for the (admittedly very minor) breaking change.

[bmos]

That's probably the better approach, they're not really in scope and I didn't think of them as breaking when I made them

[shaunagm]

Thanks for making the changes @bmos!