revert(deps): restore the @nextcloud/vue pin — the experiment answered (#446)

The experiment in #443 has its answer, and it is the one that keeps the
pin: E2E on 9.11 failed with the SAME ELEVEN tests and the SAME
signatures as before.

  127 passed, 11 failed
    7x conditional-visibility-editor   waiting for '.vs__dropdown-option'
    4x dashboard-sharing               waiting for '.sharee-option'

That is deterministic, not load. Two independent CI runs on 9.11 produce
an identical failure set, and 9.9.0 produces none, so the NcSelect rework
is the cause.

My isolated reproduction said otherwise -- those same specs passed on a
9.11 build against a seeded launchpad-demo -- and I have not yet found
what differs between that environment and CI. That gap is real and worth
closing before the specs are adapted, because adapting them against an
environment that does not reproduce the failure fixes nothing.

So development goes back to green on the pin while that work happens,
rather than sitting red. The adaptation is still the plan; this is not a
retreat from it.

The one adaptation already understood and shipped separately is stackiq's
(#841): 9.10 turned .vs__search from the <input> into a wrapper div
around it, measured on a live build. launchpad's two failure modes are
different and not yet explained.

Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>

Author: rubenvdlinde

package-lock.json

@@ -41,7 +41,7 @@
 		"@nextcloud/initial-state": "^2.2.0",
 		"@nextcloud/l10n": "^3.4.1",
 		"@nextcloud/router": "^3.1.0",
-		"@nextcloud/vue": "^9.11.0",
+		"@nextcloud/vue": "~9.9.0",
 		"dexie": "^4.4.5",
 		"dompurify": "^3.4.14",
 		"gridstack": "^12.2.1",