fix(cli): preserve trailing dir after --template file:// URL (#245)

[ulises-jeremias]

Summary

• Fix _expand_variadic_option so values of --template / -t / other value-taking flags do not set saw_positional
• That unblocks peeling a trailing project_directory after --addons when the template is a file:// (or other) URL
• Regression tests for the CLI 0.2.10: --template URL makes trailing project_directory look like an --addons value #245 repro shape; bump CLI to 0.2.11

Fixes#245

Test plan

• uv run pytest tests/test_cli.py in packages/create-awesome-python-app (19 passed)
• CI green on this PR
• After merge: tag / publish create-awesome-python-app@0.2.11 when ready

Made with Cursor

[ulises-jeremias]

Self code review

Verdict: approve / merge

Correctness

• Root cause matches CLI 0.2.10: --template URL makes trailing project_directory look like an --addons value #245: any non-- token (including --template values like file://…) was setting saw_positional, so trailing project_directory after --addons was never peeled.
• _VALUE_TAKING_FLAGS covers the value-taking CLI options used before Typer parse (--template/-t, --set, --pin, --refresh, --cache-dir, --fixture, plus --addons/--extend).
• Existing peel behavior (len(values) >= 2 at EOS) preserved; prior 0.2.9 cases remain covered by tests.

Tests

• New test_expand_preserves_dir_after_template_file_url covers the issue repro, space-separated addons after file://, and -t.
• Local + CI test / scaffold smoke green.

Notes (non-blocking)

• --addons/--extend in the frozenset are mostly defensive (those flags take the dedicated branch); harmless.
• Boolean flags (--force, --no-install, …) correctly are not in the set, so a following path still counts as the positional.

CI is green including markdownlint + MegaLinter. Merging and tagging create-awesome-python-app@0.2.11.