Fix flake.lock bump host check regressions

[Copilot]

The scheduled flake.lock bump started failing in check-hosts on redo-2 and romeo-2. This updates the repository-side compatibility shims needed for the bumped inputs to evaluate those hosts again.

• Home Manager MCP command typing

  • Convert the AWS support MCP launcher from a derivation value to a string path so it satisfies the current Home Manager programs.mcp.servers.*.command type.

  programs.mcp.servers.aws-support-mcp-server = {
    command = "${awsSupportLauncher}";
  };

• nixarr Jellyfin compatibility shim

  • Extend the existing local nixarr patch to include the Jellyfin 10.11.11 OpenAPI hash required by the bumped lockfile inputs.
  • Keep the workaround scoped to the existing romeo-2-specific shim rather than changing shared flake input behavior.

• Scope

  • No unrelated refactors.
  • flake.lock bump branch remains intact; only the minimal config fixes needed for host evaluation were added.