Add docs infrastructure and uv fixes

[antirotor]

Changelog Description

Add infrastructure to generate API documentation.

Additional review information

This PR is also fixing bugs in powershell tool script about uv logic

Testing notes:

• all deps should be installed as expected
• docs should be build

[MustafaJafar]

@antirotor About MK docs, The current setup, relies on:

• mkdocs.yml
• mkdocs_requirments.txt
• mkdocs_hooks.py
• docs folder
• deploy_mkdocs.yml

Same changes here actually: ynput/ayon-houdini#306
and it can be tested from cli as shown in ynput/ayon-core#1441

[MustafaJafar]

This PR is also fixing bugs in powershell tool script about uv logic

Where 😅? I didn't find any changes related to powershell or uv.

[iLLiCiTiT]

I'm against this pre commit hook. This is just annoying and everybody will ignore the error anyways. The PR should have linting validation instead.

When I just want to commit my current changes to "keep progress" I really don't care about it being ruff valid.

[BigRoy]

Anything that's invisible and doesn't block me is fine - like end-of-file-fixer or whatever. Those that may block me should just run on the PRs - however, if those are cosmetic things that then take a long time to fix or comment on in average PRs then having them fixed beforehand does make it worth our while.

[MustafaJafar]

Any idea how this will work when someone forks the addon?
I guess it won't work as they won't be able to provide the necessary secrets.

but isn't it the same case with forking any other addon with our github workflows.

[MustafaJafar]

I was trying to test the mk generation but it gave me 404 maybe because I was not able to access actions. (can't even see actions tab).

gh workflow run deploy_mkdocs.yml --ref feature/ci-mkdocs-with-enhancements

Never mind, I'm going to test it via a different way.
well, this doesn't work https://docs.ayon.dev/ayon-addon-template/latest yet.

[MustafaJafar]

These are for testing. They should be removed before merging the PR.