API docs theme styling setup

[travisavc]

Fixed main logo in /docs: #37

Created both a pydoctor and typedoc folder in root for continued theming
Setup pydoctor overrides for stylesheet/head of templates --- /api now has an orange header and white text to demonstrate styling is setup and ready for a deeper attack
Typedoc theming is next...continued effort!

[travisavc]

@thesteve0 not sure why this is failing in the deploy preview / build process --- locally both main and this feature branch succeed during build.sh and mkdocs serve

[thesteve0]

Looks like it is an XML parsing issue.

 writing html to /home/runner/work/voxel51-docs/temp_workspace/api_docs using pydoctor.templatewriter.writer.TemplateWriter
    return expatbuilder.parseString(string)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/xml/dom/expatbuilder.py", line 922, in parseString
    return builder.parseString(string)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/xml/dom/expatbuilder.py", line 220, in parseString
    parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 13, column 71

And there is a different problem that is cause by how I am doing the builds right now. The jupyter notebooks are getting rewritten in place and so git sees this as changed files. I don't want those files checked in as changed. This is for me to fix.

I am not going to merge this for now. Let's talk on Monday to see how we can debug that parse error here.

In terms of the jupyter notebook builds, for now we have to be more selective about our git commits and just do the files we touch. I need to fix this ASAP, hopefully @tom-vx51 or @swheaton have a brilliant idea on how to fix this in the build.