Fix case-sensitive full-name parser disambiguation

[Charlie Marcotte (cmarcotte-lawzero)]

The generated full-name preference rule can ask for clarification even when a command includes the exact object names. Inform's parser lowercases the command, but the rule compares it against printed names case-sensitively. With open containers named box and red box, and an object named Ruby inside box, take Ruby from box asks which box the player means.

Make all four printed-name comparisons in the generated Does the player mean rule explicitly case-insensitive. This preserves the existing preference logic while allowing capitalized printed names.

Add native parser regressions for one- and two-object commands, mixed-case names in either argument, and original/lowercase/uppercase command input. The tests check tracked moves and the resulting object facts, including that the other container stays closed in the one-object case.

Validation:

• Before the fix: four mixed-case cases fail with clarification prompts; both lowercase controls pass.
• After the fix: 37 tests pass across textworld/generator/inform7/tests/test_world2inform7.py and textworld/envs/wrappers/tests/test_tw_inform7.py, using Python 3.13 on macOS arm64 with Inform 7 6M62.
• git diff --check passes.

This change does not alter the planner or address separate ambiguities caused by overlapping object names across command arguments.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Charlie Marcotte (cmarcotte-lawzero)]

@microsoft-github-policy-service agree company="LawZero"

[Marc-Alexandre Côté (MarcCote)]

Good catch. Thanks for the fix.