[UX] Refine command parsing to handle more variable inputs

[smooto]

We want players to be able to focus on gameplay and puzzle-solving, rather than being frustrated by a rigid command system. Our parser should be able to handle a variety of inputs to ensure a smooth user experience.

Goal
Intended output is an array of strings, ordered like so:

const action = parsed[0]; //use
const object = parsed[1]; //key
const target = parsed[2]; //door

Variable inputs with the same intent should consistently reproduce the same output (and, therefore, the same behavior from the game).

Considerations

• action aliases
• sentence structures
• word ordering

Example edge cases
base command: use key door

• use key with door -- valid
• Use the key on the door. -- valid
• on the door, use key --valid
• unlock door with key -- valid???

Resources
Natural NLP -- supports POS tagging

Rolling our own
It may be easier/more lightweight for us to create our own POS tagger from scratch. One benefit is that we can distill tagging categories to just what we need to separate wheat from chaff in our context.

Step 1: ID tags and build lexicon

POS	tag	examples
Action	ACT	use, look, take
Item	ITM	key, table, door
Particle	PRT	at, on, with

• Lexicon for "actions" includes aliases

• Particles can be used to determine targets from other objects. this ended up working inconsistently and being kind of extraneous anyway; attaching expected object-target ordering to a given action verb works better for MVP purposes

• Irrelevant text (anything not defined in the lexicon) can be disregarded.

Step 2: build out tokenizer and functions to tag tokens based on lexicon

• tokenizer

• tagger

• alias parsing

Step 3: create rulesets & functions to separate object/target, etc.

• determine target item vs object item based on position relative to particle expected ordering of items for a given action verb

• create response object to feed into parser

• flag inappropriate command structures (ex. more than two items, more than one action, etc.) for error feedback to user -- added a couple of basic things, will probably expand in separate card

Step 4: unit test and integrate

• implement remaining actions/aliases into lexicon

• lexicon for "items" pulls names directly from Mongo docs for items not strictly necessary, prob going to make a separate card for the stretchy stretch

• build out tests for each action type