perf: replace arrays with Maps in AnimationInputs for O(1) lookups

[Copilot]

Replaced array-based storage with Map-based storage in AnimationInputs to eliminate O(n) lookups. The class used arrays with .find() for retrieving inputs by name, which degrades as input count grows.

Changes

• Changed textInputs, numberInputs, toggleInputs, triggerInputs from AnimationInput<T>[] to Map<string, AnimationInput<T>>
• Updated _registerInput: array.some() → map.has(), array.push() → map.set()
• Updated _getInput: array.find() → map.get()
• Updated update: iterate via triggerInputs.values() instead of direct array iteration

Impact

Public API unchanged. All lookups now O(1) instead of O(n).

// Before: O(n) scan through array
private _getInput<T>(name: string, animationInputArray: AnimationInput<T>[]) {
  return animationInputArray.find((input) => input.name === name) ?? null;
}

// After: O(1) map lookup
private _getInput<T>(name: string, animationInputMap: Map<string, AnimationInput<T>>) {
  return animationInputMap.get(name) ?? null;
}

Original prompt

Work on TODO: Performance - Replace textInputs, numberInputs, toggleInputs, and triggerInputs with maps (from src/animations/types/AnimationInputs.ts)

Created from VS Code via the GitHub Pull Request extension.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.