Update the on-boarding documenation

[mikegros]

Documentation is a bit out of date and we really could use nice "Getting Started" documentation for new users

[mikegros]

• Make sure the examples run smoothly and maybe point at config files to easily change endpoint
• Make sure docs and mkdocs are updated so that the documentation is working and updated.
• Move information from the README to the webpage documentation.

[mikegros]

This needs to be set for JOSS

[awadell1]

Docs should probably use autodocs (or similar) over the current hard-coded docs (ie. below):

ursa/docs/execution_agent.md

Lines 20 to 27 in 267b566

	## Parameters
	When initializing `ExecutionAgent`, you can customize its behavior with these parameters:
	| Parameter | Type | Default | Description |
	|-----------|------|---------|-------------|
	| `llm` | `BaseChatModel` | `init_chat_model("openai:gpt-5-mini")` | The LLM model to use |
	| `extra_tools` | `Optional[list[Callable[..., Any]]]` | `None` | Additional tools for the execution agent |

[jmohdyusof]

Note that the online docs already builds the API Reference from the docstrings, so the issue might be not having redundant or conflicting information here. Maybe more more high-level overviews of the design of the agents (like you presented in the talk today) and then refer to the API Reference for these type of details

[jmohdyusof]

My suggestion is basically to use the MkDocs to include some subset of the doc strings in the individual agent markdown. For example, I can add a reference section to docs/execution_agent.md, to replace the Parameters section in that file.

## Reference

::: ursa.agents.execution_agent.ExecutionAgent