Normalize the Windows launcher so a fresh clone is not born dirty

[lwrage]

Every clone of this repository reported an immediate uncommitted modification:

$ git clone https://github.com/osate/aadl-tooling.git && cd aadl-tooling
$ git status --porcelain
 M vscode-extension/server/aadl/bin/aadl-standalone.bat

Nothing was actually modified. The blob was committed with CRLF before .gitattributes existed; the *.bat text eol=crlf rule I added alongside CI tells Git the index holds LF and to emit CRLF on checkout. So git status normalizes the working tree back to LF, compares it against a CRLF index, and reports a permanent difference.

git add --renormalize rewrites the index entry as LF, which is what the attribute already assumed. Checkouts still materialize CRLF, so the launcher keeps the line endings cmd.exe needs — verified in a fresh clone:

CLEAN (fixed)
launcher line endings: DOS batch file text, ASCII text, with CRLF line terminators

How it surfaced

The new -dirty provenance marker from #6 fired on a pristine actions/checkout:

warning: packaging a CLI built from a dirty tree
  (ls.commit=5a27deea6bd75277524b4da7ecc85fb17d2bf81c-dirty)
  language server 0.1.0.v20260902-1520 (5a27dee...-dirty)
  OSATE           2.19.0.vfinal (425614884eaf14312141fbdd3a393ba54ff34b23)

Which made the marker useless — it fired on every build and so distinguished nothing. Worth being clear that the marker was working correctly and faithfully reporting what git told it; the defect was in .gitattributes, which I introduced in #1. This is the kind of thing that only shows up once something starts depending on git status being meaningful.

Also worth noting for anyone who has cloned already: this affected every contributor's git status output, not just CI.