Refactor Player from generic class to inheritance hierarchy

[gausie]

Summary

• Replaces Player<IsFull extends boolean> generic with a Player + Player.Profiled class hierarchy (inspired by Discord.js patterns)
• Adds a Players manager domain (kolClient.players.resolve() / .fetch() / .getNameFromId()) that owns caching and lookup logic
• Deletes Cache.ts (absorbed into Players)

Design

// Base Player — lightweight identity from search/chat
const player: Player = await kolClient.players.resolve("gausie");
player.id;        // number
player.name;      // string
player.toString() // "gausie (#1197090)"

// Player.Profiled — full data from profile page, extends Player
const profiled: Player.Profiled = await kolClient.players.fetch("gausie");
profiled.ascensions;  // number (guaranteed present)
profiled.avatar;      // string

// Narrowing via instanceof
if (player instanceof Player.Profiled) {
  player.ascensions; // works
}

// Upgrade: Player → Player.Profiled
const profiled = await player.fetch(); // Player.Profiled | null
const same = await profiled.fetch();   // Player.Profiled (no null — already profiled)

What's better vs the generic approach:

• No conditional types, no as unknown as Player<true> casts, no If<> helper
• instanceof narrowing — standard TypeScript, no custom type guards
• Covariant return type on fetch() — calling on Player.Profiled returns Player.Profiled (not null)
• Surfaces a real bug: winner.player.createdDate in Raffle was always null (removed from the createRaffleWin call)