docs(): generate docs for our Python SDK

[hsheth2]

It looks a little something like this:

• I've manually picked a few modules that I consider to be part of our public interface for the initial version, but it's extremely easy to add more.
• This will set up the scaffolding for us to autogenerate CLI reference material too.

Issues

• Not sure if this is the best place to put these in the docs - perhaps we need a "reference" section?
• The autogenerated docs pages can be pretty long and hence hard to navigate.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[laulpogan]

I'd have them live under python sdk in tools as "SDK reference"
We could thinking about moving the SDK's into the API bucket too

[hsheth2]

@laulpogan I've moved them to a Python SDK Reference section

Let me know what you think - we can use the vercel live preview now :)

[jjoyce0510]

Margin between classes could make things a bit more readable... Let's see if our friend Jeff can take a look