feat(api): implement Pawn Social subsystem and REST endpoints

[IlyaChichkov]

This PR introduces the PawnSocialController and its backing service, exposing RimWorld's social and relationship systems to the REST API. It allows clients to query real-time interaction readiness, extract deep historical interaction logs, view opinion breakdowns, and actively manipulate relationships or force interactions.

New Endpoints

Queries (GET)

/api/v1/game/defs/interactions: Lists all valid InteractionDef types.

/api/v1/pawns/interactions: Returns a pawn's current readiness to interact (cooldown ticks and status).

/api/v1/pawns/interactions/log: Retrieves the parsed historical interaction log (who, what, and translated grammar text).

/api/v1/pawns/relations: Returns all established familial/social bonds, explicitly bypassing cache limits to include dynamic "Friend/Rival" thresholds and modded Familiars.

/api/v1/pawns/opinions: Retrieves a map-wide numerical opinion matrix for the pawn, including a specific breakdown of social memories (e.g., "Chitchat +5", "Insulted -15").

Actions (POST/DELETE)

/api/v1/pawns/interactions/force: Forces a specific social interaction between two pawns via the game's native AI router.

/api/v1/pawns/relations/add: Instantly creates a direct social relation bond.

/api/v1/pawns/relations/remove: Severs a specific social relation bond.

[jkbennitt]

Review

Comprehensive social API — interactions, relations, opinions, force/add/remove. Follows the established controller pattern (direct service calls, main-thread execution via the request queue pipeline). One compilation blocker.

1. Compilation error in GetPawnOpinions — st vs t (blocker)

Line 297: foreach (var st in socialThoughts) but line 299 uses if (t is Thought_SituationalSocial ss ...). Loop variable is st, body references t. This won't compile. Likely needs st throughout (or rename the loop variable to t).

Minor / Suggestions

• Hardcoded 120-tick cooldown (line 276): Magic number — worth a comment documenting the source in RimWorld's interaction system.
• Reflection fragility: PlayLogEntry_Interaction fields (initiator, recipient, intDef) accessed via reflection. If field names change across RimWorld versions, entries silently return null. A one-time log warning when field resolution fails would help.
• No pagination on interaction log: GetPawnInteractionLog iterates all PlayLog.AllEntries. On long colonies this could be hundreds of entries. A ?limit=N query param (defaulting to e.g. 50) would be useful.
• DELETE with JSON body: RemoveRelation uses DELETE with a request body. Some proxies/clients strip bodies from DELETE requests. Query params would be more portable.

What's good

• Comprehensive scope — 8 endpoints covering the full social subsystem
• Reflection fields cached outside loops in interaction log parsing
• entry.Concerns(pawn) fast-path filter before heavier reflection work
• Graceful empty-list handling when PlayLog is null
• Bruno collection covers all endpoints
• Follows established DDD controller pattern