chore: remove release-as 0.1.0 pin after 0.1.0 ships

[SebTardif]

Why

PR #200 set release-as: "0.1.0" in release-please-config.json so the next release is 0.1.0 instead of 0.0.10.

Leaving release-as after the release lands causes release-please to keep forcing 0.1.0 (or block normal bumps).

Done when

• Extension 0.1.0 is published (Marketplace / Open VSX / GitHub Release tag patchloom-v0.1.0)
• "release-as": "0.1.0" is removed from release-please-config.json on main
• bump-minor-pre-major: true remains (breaking changes stay minor pre-1.0)
• No bump-patch-for-minor-pre-major (feat commits keep bumping minor under 1.0)

Related

• Config: chore: target next release-please cut as 0.1.0 #200
• Release PR: chore(main): release patchloom 0.1.0 #199