Set ESLint to warn on `ts-ignore` comment

Editor assessment

Using `refactor` for an ESLint configuration change is arguable: no production code is reshaped, so `chore` would communicate 'tooling only' more accurately and keep refactors meaningful for reviewers. The subject itself is good — lowercase, imperative, and concrete about the rule involved ('set ESLint to warn on `ts-ignore` comment'). The body's ':shirt: Set `ban-ts-comment` to warn on @ts-ignore' adds the actual rule name, which the header omits, but the gitmoji prefix is decorative noise. A sentence explaining why @ts-ignore should be discouraged (safer @ts-expect-error adoption, catching stale suppressions) would justify the policy shift for future archaeologists.