Fix extract-basic standalone uv sync (llama-cloud-fake path dep) (#267)

* Resolve extract-basic llama-cloud-fake from PyPI when standalone

- Drop path override in templates/extract-basic; depend on published 0.1.x
- Add templates/extract-basic to uv workspace members so monorepo still uses local editable package
- Relax root click pin to match templates (8.3.0 is broken)

* Revert adding extract-basic to uv workspace

llamactl dev validate runs uv run from the template dir, which walks up to
the workspace venv — where llama-agents-appserver isn't installed. Keep
extract-basic standalone; published llama-cloud-fake resolves fine in the
monorepo too.

* Bump llama-index-workflows floor to 2.16.0 across templates

basic, document-qa, human-in-the-loop, rag, web-scraping were lagging on
2.2-2.5; align with the rest of the fleet.

* Wire data-extraction tests with llama-cloud-fake, add to uv workspace

- clients.py installs FakeLlamaCloudServer when FAKE_LLAMA_CLOUD is set
- conftest.py flips the env var before test imports
- Real test_workflow.py exercises process_file against the fake and
  checks metadata_workflow returns the configured schema/collection
- Bump all versions in .github/templates-remotes.yml for changed templates

pyproject.toml

@@ -31,12 +31,6 @@ dev = [
     "llama-cloud-fake>=0.1,<0.2",
 ]
 
-# Until llama-cloud-fake is published to PyPI, resolve from the monorepo
-# workspace. Remove this block once the package is on PyPI and the above
-# version pin can resolve normally.
-[tool.uv.sources]
-llama-cloud-fake = { path = "../../packages/llama-cloud-fake", editable = true }
-
 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"