(doc) add svg file support documentation

[edknv]

Description

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.
• If adjusting docker-compose.yaml environment variables have you ensured those are mimicked in the Helm values.yaml file.

[greptile-apps]

Greptile Summary

This PR documents SVG file support in the supported file types list (overview.md) and the installation guide (README.md), correctly noting the library-only availability and the optional cairosvg dependency. The only finding is a minor inconsistency on nemo_retriever/README.md line 203 where the prose says pip install cairosvg but the code block directly below it uses uv pip install "nemo-retriever[svg]" — the prose should be updated to match the project's uv-based toolchain.

Confidence Score: 5/5

Documentation-only PR is safe to merge.

Both changed files are markdown documentation with no code changes. The single finding is a P2 prose/code inconsistency that does not affect functionality.

nemo_retriever/README.md has a minor prose inconsistency on line 203 (pip vs uv pip).

Important Files Changed

Filename	Overview
docs/docs/extraction/overview.md	Adds svg to the supported file types list with correct library-only and cairosvg dependency notes; alphabetically ordered correctly.
nemo_retriever/README.md	Adds SVG installation instructions; minor prose inconsistency references pip install while the code block below uses uv pip install.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User wants SVG support] --> B{Deployment mode?}
    B -- Library Mode --> C[uv pip install nemo-retriever svg]
    B -- Container Mode --> D[Not supported]
    C --> E[cairosvg>=2.7.0 installed]
    E --> F[SVG files can be ingested]
    D --> G[Use a different file type]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: nemo_retriever/README.md
Line: 203

Comment:
**Prose references `pip` instead of `uv`**

The sentence tells users to run `` `pip install cairosvg` `` but the code block immediately below uses `uv pip install`. Since the project's standard tooling is `uv`, the prose should align with the code block to avoid confusion.

```suggestion
For SVG files, install the optional `cairosvg` dependency. SVG support is available in the NeMo Retriever Library, but not in the container deployment. `cairosvg` requires network access to install, so it will not work in air-gapped environments.
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (3): Last reviewed commit: "Update nemo_retriever/README.md" | Re-trigger Greptile}

[kheiss-uwzoo]

changed the sentence structure