Documentation facelift

[wiseodd]

Closes #226.

I decided to use mkdocs-material, which is the standard in Python (see Astral's docs etc.).

@aleximmer, I added a deploy workflow. Could you disable the current one for pdoc? (Seems like it's hidden in the repo settings page.)

To review:

uv sync --all-extras
uv run mkdocs serve

then open localhost:8000

[aleximmer]

Thanks a lot for updating the docs. They look super good now 💯

I got some warnings when running uv run mkdocs serve, not sure if these are serious:

SyntaxWarning: invalid escape sequence '\i'
             File "Laplace/.venv/lib/python3.12/site-packages/_griffe/agents/visitor.py", line 203, in get_module
               top_node = compile(self.code, mode="exec", filename=str(self.filepath), flags=ast.PyCF_ONLY_AST, optimize=1)
             File "Laplace/laplace/lllaplace.py", line 510, in
               """Here not much changes in terms of GP inference compared to FunctionalLaplace class.

It also shows us some docstring parameter descriptions that we should fix:

WARNING -  griffe: laplace/baselaplace.py:1957: Parameter 'num_data' does not appear in the function signature
WARNING -  griffe: laplace/baselaplace.py:1957: Parameter 'diagonal_kernel' does not appear in the function signature
WARNING -  griffe: laplace/baselaplace.py:1957: No types or annotations for parameters ['See']
WARNING -  griffe: laplace/baselaplace.py:1957: Parameter 'See' does not appear in the function signature
WARNING -  griffe: laplace/utils/matrix.py:296: Parameter 'dampen' does not appear in the function signature
WARNING -  griffe: laplace/utils/subnetmask.py:361: No types or annotations for parameters ['parameter_names']
WARNING -  griffe: laplace/utils/subnetmask.py:361: Parameter 'parameter_names' does not appear in the function signature

Should we open an issue to fix it after the PR?

For deploying the docs, I will disable the old docs once you merge.

[runame]

Haven't looked at this in detail yet, but looks good! Feel free to just merge.

[wiseodd]

@aleximmer fixed the issues. For the improper docstrings, I agree, let's open an issue for this. I also want to refactor the codebase to make it more extendible.

Feel free to merge and test whether the new docs site is properly deployed.