docs: fix case-conversion casing examples

[clockwork-labs-bot]

Description of Changes

Fix docs examples that still used pre-case-conversion names after the default case-conversion work in #4263 and follow-up casing work in #5286/#5434.

This PR:

• Updates the incremental migrations transcript so reducer argument JSON uses camelCase enum variants (fighter, good) and SQL output shows canonical enum variant names (fighter, neutral, good).
• Updates C# quickstart and chat tutorial CLI/SQL commands to use canonical reducer/table names (send_message, person, message) rather than generated C# API names.
• Corrects the C# client reference reducer API description from Rust-style snake_case methods to generated C# PascalCase methods/events (SetName, OnSetName, RemoveOnSetName).
• Clarifies the TypeScript client reference after Fix TypeScript table handle casing #5286: generated table/view handles use camelCase accessor handles, with deprecated snake_case aliases where generated.
• Normalizes SQL reference examples to lower canonical table names so examples match the default case-conversion policy.

Related external PRs that prompted this audit: #5566 and #5569.

API and ABI breaking changes

None. Docs only.

Expected complexity level and risk

1

Low-risk documentation correction. The main risk is wording accuracy around generated accessor names, so the changes were checked against the merged case-conversion PRs and generated binding examples.

Testing

• git diff --check
• pnpm --dir docs build