feat!: raise the VS Code floor to 1.136

[kkdev92]

Releases 5.0.0. engines.vscode moves from ^1.134.0 to ^1.136.0; nothing
else about the package changes.

Why

@types/vscode published 1.136.0. This package's floor tracks it, because the
types decide the newest API the source may name, and vsce refuses to package
an extension whose @types/vscode outruns its engines.vscode. Raising only
the types would let code compile against an API the declared floor does not
have, so the two move together.

Extensions built on this package inherit the floor and must declare at least
^1.136.0 themselves. That inheritance is what makes this a major rather than a
minor.

The API did not change

dist/, src/ and bin/ are byte-for-byte what 4.1.1 shipped. This was
measured rather than asserted: the published 4.1.1 tarball was downloaded and
unpacked, a fresh npm pack was taken of this tree, and the two were compared
directory by directory. Only package.json, README.md and CHANGELOG.md
differ.

One sentence reworded rather than renumbered

The requirements section said the floor was 1.134.0 "because that is the newest
@types/vscode there is". That was true when written and false the day 1.136.0
shipped, and nothing failed in between. Renumbering it would buy until the next
types release. It now states the rule the floor follows, so there is no fact
about the registry left to go stale.

Verification

• npm run quality — format, five typecheck projects, lint, 1087 tests with
  coverage, knip, TypeDoc
• npm run verify:package — every subpath imports, require() is refused, the
  README samples typecheck against the packed types, the CLI runs from the
  installed package
• Both real-host contract lanes at the new floor. The Extension Host and web
  fixtures each report VS Code 1.136.1, so the floor was exercised against a
  host that actually has it rather than only against fakes

🤖 Generated with Claude Code