fix(tests): fix three CI failures on develop

- alliance recruiting default: change DEFAULT true → false in both
  0001_init.sql and 0004_alliance_recruiting.sql; new alliances should
  not be open for recruitment by default (TestSetAllianceRecruiting)
- guild_invites migration: add IF NOT EXISTS so re-running migrations
  on an existing DB does not fail with "relation already exists"
  (TestMigrateExistingDBWithoutSchemaVersion)
- test character name: shorten "Idem_Rollover_Leader" (19 chars) to
  "IdemRollLeader" to fit the VARCHAR(15) constraint
  (TestRolloverDailyRP_Idempotent)

server/migrations/sql/0001_init.sql

@@ -998,7 +998,7 @@ CREATE TABLE public.guilds (
     pugi_name_1 character varying(12) DEFAULT ''::character varying,
     pugi_name_2 character varying(12) DEFAULT ''::character varying,
     pugi_name_3 character varying(12) DEFAULT ''::character varying,
-    recruiting boolean DEFAULT true NOT NULL,
+    recruiting boolean DEFAULT false NOT NULL,
     pugi_outfit_1 integer DEFAULT 0 NOT NULL,
     pugi_outfit_2 integer DEFAULT 0 NOT NULL,
     pugi_outfit_3 integer DEFAULT 0 NOT NULL,

server/migrations/sql/0004_alliance_recruiting.sql

@@ -1 +1 @@
-ALTER TABLE public.guild_alliances ADD COLUMN IF NOT EXISTS recruiting boolean NOT NULL DEFAULT true;
+ALTER TABLE public.guild_alliances ADD COLUMN IF NOT EXISTS recruiting boolean NOT NULL DEFAULT false;

server/migrations/sql/0012_guild_invites.sql

@@ -2,7 +2,7 @@
 -- player-initiated applications. This gives each invitation a real serial PK
 -- so the client's InvitationID field can map to an actual database row
 -- instead of being aliased to the character ID.
-CREATE TABLE guild_invites (
+CREATE TABLE IF NOT EXISTS guild_invites (
     id           serial PRIMARY KEY,
     guild_id     integer REFERENCES guilds(id),
     character_id integer REFERENCES characters(id),