v0.14.0 — add_many accepts --project alongside --json

Fixed

ticketgraph add_many --project X --json '{"tickets":[...]}' now works.

Previously --json was only recognised as the first token and had to be the sole input, so combining it with --project failed with add_many requires --json, an error telling you to do what you had just done. Dropping --project to get past it made add_many resolve the project from the current directory instead: exit 0, a created=[...] line, and the tickets landing in a different project from the one intended. From the caller's side that looked like a batch create that printed success and created nothing.

--json is now recognised at any position and merged with ordinary flag parsing, so --project (and any other scalar flag) behaves the same way it does for add. Setting the same key through both channels is a usage error rather than a silent last-wins, and --json given twice or with no value is still rejected.