Split VROOM settings into admin and organization controls

[roncodes]

Summary

• split the VROOM settings UI into dedicated admin and organization components
• add app re-exports and extension wiring for the new settings surfaces
• add scoped server-side settings handling for admin and organization VROOM configuration

Changes

• replace the old single vroom-settings component with admin/vroom-settings and organization/vroom-settings
• add organization save-task integration so VROOM settings can participate in the existing settings save flow
• add support for api_key, api_host, and endpoint_mode at both the admin and organization level
• update the VROOM controller, support classes, config, and routes to serve the new scoped settings endpoints
• refresh package metadata and lockfiles for the current dependency state

Why

This keeps global VROOM defaults separate from per-organization overrides, which makes the settings UX clearer and allows organizations to opt into their own server configuration without conflating it with system-level defaults.