Allow multiple simultaneous console viewers for KVM user VMs

### The required feature described as a wish

##### ISSUE TYPE

* Feature Idea

##### COMPONENT NAME

~~~text
KVM / Console Proxy
~~~

##### CLOUDSTACK VERSION

~~~text
Behavior reproduced on 4.22.1.0.
Feature implementation targets current main (4.23.0.0-SNAPSHOT).
~~~

##### CONFIGURATION

KVM user VMs using the standard CloudStack Console Proxy / noVNC console.

##### OS / ENVIRONMENT

KVM-based CloudStack environment.

##### SUMMARY

Currently, when two users attempt to access the console of the same KVM user VM,
opening the second console disconnects the first viewer.

The Console Proxy already supports using a unique console session UUID as the
viewer key when `sessionRequiresNewViewer` is enabled. This capability can be
used to allow multiple simultaneous console viewers for KVM user VMs.

The proposed change adds a global setting:

`consoleproxy.kvm.multiple.viewers.enabled`

The setting defaults to `false` to preserve the existing single-viewer behavior.

When enabled, each console request for a KVM user VM receives a unique viewer
session so multiple users can remain connected to the same VM console
simultaneously.

The change is restricted to KVM user VMs and does not alter console behavior for
system VMs or other hypervisors.

##### STEPS TO REPRODUCE

~~~text
1. Start a KVM user VM.
2. Log in to CloudStack as User A and open the VM console.
3. Log in separately as User B and open the console of the same VM.
4. Observe User A's console session.
~~~

##### EXPECTED RESULTS

~~~text
Both users should be able to remain connected to the same VM console when
multiple console viewers are enabled.
~~~

##### ACTUAL RESULTS

~~~text
Opening the console as User B disconnects the existing console session for
User A.
~~~

Beginnen Sie damit, die bestehende Console Proxy-Verarbeitung für KVM-Benutzer-VM-Konsolenanforderungen und das Verhalten von sessionRequiresNewViewer nachzuverfolgen. Überprüfen Sie, wie sich die neue Einstellung consoleproxy.kvm.multiple.viewers.enabled auf Viewer-Sitzungen auswirken sollte, und bewahren Sie dabei das aktuelle Verhalten bei deaktivierter Einstellung sowie für System-VMs oder andere Hypervisoren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.