fix(cli): write pyproject.toml once when scaffolding a new agent

[vldcmp-uipath]

Problem

Four scaffolds called generate_pyproject twice per uipath new run — once before generating the project files, once after:

with console.spinner(...):
    generate_pyproject(directory, name)     # <-- overwritten below
    generate_script(directory)
    console.success("Created 'main.py' file.")
    console.success("Created 'google_adk.json' file.")
    generate_pyproject(directory, name)
    console.success("Created 'pyproject.toml' file.")

The second call rewrote the first with identical content, so nothing was visibly wrong, but the generation order differed from the other integrations for no reason, and anything written to pyproject.toml between the two calls would be silently discarded.

Changes

• uipath-agent-framework, uipath-google-adk, uipath-llamaindex and uipath-openai-agents now generate the script and config first, then write pyproject.toml once — the order uipath-claude-sdk and uipath-pydantic-ai already used. Those two packages are unaffected and not touched.
• A regression test per package counts the calls, so the duplication cannot come back.
• uipath-agent-framework's failure test now runs in its own working directory. The middleware scaffolds into the cwd, and with the redundant first call gone, the generation that precedes the induced failure writes real files — which landed in the source tree.
• uipath-llamaindex had no test for its scaffolding middleware; it gets one covering the files written and the project name.
• Patch bumps: uipath-agent-framework 0.1.1, uipath-google-adk 0.1.1, uipath-llamaindex 0.6.2, uipath-openai-agents 0.1.2.

No dependency or middleware-contract changes, so this is independent of UiPath/uipath-python#1886 and can merge on its own.

Testing

Full suites pass in every touched package (166 / 125 / 166 / 68), with mypy --config-file pyproject.toml ., ruff check and ruff format --check clean in each.

🤖 Generated with Claude Code

[vldcmp-uipath]

Closing: UiPath/uipath-python#1886 fixes #1543 entirely in the base CLI, so no integration in this repo needs a change — uipath new simply doesn't consult the new middleware chain for a function project.

Recording what this PR had found, in case someone picks it up later: uipath-agent-framework, uipath-google-adk, uipath-llamaindex and uipath-openai-agents call generate_pyproject twice per scaffold — once before generating the project files and once after. The second call rewrites the first with identical content, so nothing is visibly broken today; it only matters if anything is written to pyproject.toml between the two calls, and it leaves the generation order inconsistent with uipath-claude-sdk and uipath-pydantic-ai. The branch fix/gate-new-middlewares-on-project-type keeps the one-line-per-package fix, regression tests, and a first scaffolding test for uipath-llamaindex.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud