:book: First release functionality

[daquinteroflex]

Here we can consolidate the initial set of functionality, and reference where similar things have been attempted or implemented in different sphinx extensions. These can then be migrated to specific issues accordingly.

• Document classes and methods as we want users to access them, not corresponding to their location in the API
• Non duplicated classes on the API toctree.
• Auto document methods? #9
• Docs Suggestion: Example section introductions #10
• Exclude some fields from documentation without making them private #11
• Enable ordering of API methods in a more configurable manner. #12
• Enable shorthand API name ie. tidy3d.web.run instead of tidy3d.web.api.webapi.run #14
• Move hacked BaseClass docs definition into this extension #15
• Add CI tests for verification of the built documentation with tidy3d and flow360 classes latest versions #16
• Implement custom html styling in this extension #18
• Functionality to check for broken links in built docs #20
• Enable equations in the parameters descriptions, or full parameter #21
• Evaluate how to link jupyter-book and our website integrated in a html build correctly.

Required functionality to demo the project:

• Create demo documentation directory that uses the extension we can host and test.
• Create architecture of the target directives implementation accordingly.
• Create representative demo API python functions.
• Implement the set of directives we believe can implement some of the functionality we desire.

Nice to have:

• Implement more docs website interactive animations #26
• Implement a CI script so that we can see live docs for each PR #27