Sync from umple-lsp@15af303 (both, v0.1.2)

[DraftTin]

Auto-sync from umple-lsp

Source: umple-lsp@15af303d6bb85c1d7bf98928adc814e2a0aabd9a
Change type: both (grammar = grammar.js/parser.c, highlights = queries/**.scm)
Version bump: 0.1.1 → 0.1.2

Changed paths in umple-lsp

packages/tree-sitter-umple/grammar.js
packages/tree-sitter-umple/queries/completions.scm
packages/tree-sitter-umple/queries/definitions.scm
packages/tree-sitter-umple/queries/highlights.scm
packages/tree-sitter-umple/queries/references.scm
packages/tree-sitter-umple/src/parser.c

Safe to merge?

• highlights only — safe to merge now.
• grammar or both — wait for an umple-lsp-server npm
  publish that includes matching server-side indexer support
  before merging, if the new syntax requires it. Check the
  latest published server with npm view umple-lsp-server version.
  If you merge early, editor highlighting may understand new
  syntax before the LSP does; users will see a temporary
  feature gap until npm catches up.

Next steps after merge

1. (Optional) publish umple-lsp-server to npm if the server
   changed alongside this grammar.
2. Cut a new marketplace release by updating the git submodule
   pointer and extensions.toml umple entry version in a fork
   of zed-industries/extensions, then opening a PR there.
   This stays manual by design (topic 040).

---

Produced by .github/workflows/sync-umple-zed.yml in umple-lsp.
Re-runs on subsequent grammar / highlight pushes force-push onto
sync/umple-lsp-master to coalesce with this PR instead of stacking new ones.