chore(release): set main to 1.9.5

The stable tag is published and every byte of it is already on main —
the release branch was built entirely from cherry-picks, so the only
thing main still lacks is the version number itself.

Doing this instead of merging the sync PR the promote workflow opened.
That PR replays 26 commits, 23 of which are the cherry-picks main
already has under different SHAs, and one of those (db101b9) touches
NewEditorShell.tsx — the same file 210e5da changed after the release
branch forked. Rebasing a stale version of that file over a newer one is
how a merge silently drops the newer change, and the workflow's own
rebase already failed five times against it. `feat(editor): delete a
project from the Open project dialog` is deliberately held for 1.10 and
must survive this sync.

Verified before writing: `git diff main v1.9.5` is empty across every
path except package.json, package-lock.json, and the files that feature
adds.

Author: EtienneLescot

package-lock.json

@@ -1,7 +1,7 @@
 {
 	"name": "openscreen",
 	"private": true,
-	"version": "1.9.2",
+	"version": "1.9.5",
 	"type": "module",
 	"packageManager": "npm@10.9.4",
 	"engines": {