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]

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]

I get this on windows

Line |
 160 |      Write-Color -Text ">>> ", "Test if UV is installed ... " -Color G …
     |      ~~~~~~~~~~~
     | The term 'Write-Color' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling
     | of the name, or if a path was included, verify that the path is correct and try again.

[MustafaJafar]

tools/manage.ps1 ruff-check

raise a lot of things.

Are the Ruff rules a lot than what we used to have?

[MustafaJafar]

I get this from this command.

>>>  Cleaning cache files ... OK
error: Failed to spawn: `mkdocs`
  Caused by: program not found

[MustafaJafar]

this one has the same result as in https://github.com/ynput/ayon-addon-template/pull/12/changes#r3011399207

btw running uv build docs returns

E:\Ynput\ayon-addon-template>uv build docs                
Building source distribution...
  × Failed to build `E:\Ynput\ayon-addon-template\docs`
  ╰─▶ E:\Ynput\ayon-addon-template\docs does not appear to be a Python project, as neither `pyproject.toml` nor `setup.py` are present
      in the directory

[MustafaJafar]

btw, I don't have access to Actions tab in this repo and not sure why the
https://docs.ayon.dev/ayon-addon-template/latest doesn't have something yet.

[MustafaJafar]

btw, the way our uv setup works is as follows:
These work on my side.
Also, I believe it can't serve the site without building it in the first place.

uv pip install -r mkdocs_requirements.txt
uv run mike deploy 0.0.0
uv run mike deploy --update-aliases 0.0.0
uv run mike set-default latest
uv run mike serve

uv run mike delete 0.0.0

[iLLiCiTiT]

For me, pre-commit hooks are the worst, especially if they do changes automatically, that's why we have linter to validate it.