Refactor AdminSettings

[Antreesy]

Currently components in AdminSettings do not have a shared state, and data exchange could only be done with EventBus:

spreed/src/components/AdminSettings/SignalingServers.vue

Lines 168 to 173 in fe2dd66

	success: () => {
	showSuccess(t('spreed', 'High-performance backend settings saved'))
	EventBus.emit('signaling-servers-updated', this.servers)
	this.loading = false
	this.toggleSave()
	},

Expected behaviour

• 🍍 Shared Pinia store and gradual migrate of useful data to it (currently HPB settings, SIP settings) currently an overkill
• Move shared state to the AdminSettings.vue:
  • signaling settings
  • signaling features
  • sip settings
• 📘 Additionaly migrate to `<script setup lang="ts">
  • AdminSettings.vue (1 usage found)
  • AllowedGroups.vue (1 usage found)
  • BotsSettings.vue (1 usage found)
  • Federation.vue (1 usage found)
  • GeneralSettings.vue (1 usage found)
  • HostedSignalingServer.vue (1 usage found)
  • MatterbridgeIntegration.vue (1 usage found)
  • RecordingServer.vue (1 usage found)
  • RecordingServers.vue (1 usage found)
  • SignalingServer.vue (1 usage found)
  • SignalingServers.vue (1 usage found)
  • SIPBridge.vue (1 usage found)
  • StunServer.vue (1 usage found)
  • StunServers.vue (1 usage found)
  • TurnServer.vue (1 usage found)
  • TurnServers.vue (1 usage found)
  • WebServerSetupChecks.vue (1 usage found)

[ShGKme]

Admin settings is a simple single page with low-height component tree depth. Let's not introduce a global app-level state here (we have it more than should already).

If I'm not wrong, the only shared state here is the signaling servers. And it is only used in direct children of AdminSettings.

We can store it in the AdminSettings as a single source of common admin settings data, and directly pass it to children via props, updating via events.

[nickvergessen]

Also sipbridge is referenced by another setting (soon, PR is there and awaiting merge)