Improve `ToString` for comparison operator tokens.
comment about future refactoring
comment only change
REFACTOR: Make all keyword terms into fields.

Since many of them are also C# keywords, I am using @syntax.

The spec doesn't call out `-split` and the like as keywords, so I didn't do those... but we may need to.
Stop marking `comparison_operator` as transient.

It wasn't really helping, and marking as transient can make the parse tree a little more confusing, and I got to extract a method.
FORMATTING: Format all documents after merging from @alesliehughes
add copyright messages
Merge pull request #68 from JayBazuzi/cleanup

Formatting and copyright messages
Fix parsing of `if ($true) { }`

The whitespace between the braces was confusing the parser. I can't say I
understand why.

Added a test case for a conditional with a more complex condition, I've
seen this cause bad parsing results - there are so many different parts
of the grammar at play here, and ambiguity is a possible problem.
Parsing of `-ne` expressions.

Oddly, this worked:

    1 -eq 2

but this failed to parse:

    1 -ne 2

Why?

When Irony scans for tokens, it uses roughly the following algorithm:

1. Based on the current state of the parser, which non-terminals are
allowed next?

2. Try to match each terminal to the current input.

3. If 2 terminals have the same priority, prefer one that matches
more of the input (be greedy)

4. Return the highest-priority terminal that matches

There's a problem here: if 2 matching terminals have the same priority
and match the same length of input, the match is non-deterministic.
This indicates a problem in the grammar definition, but it's one that's
easy to miss.

I discovered this problem while trying to test a comparison with `-ne`.
The parser sees it as either a command parameter or a comparison
operator, and was chosing command parameter. (When it saw `-eq`, it
picked comparison operator, again non-deterministically.)

The fix is to raise the priority of comparison operator terminals.

I added an exception in Irony for these ambiguities, to make it obvious
when it happens. This caused some tests to fail, because of an
ambiguity between generic and array type expressions. I temporarily
disabled those parts of the grammar.
Merge pull request #69 from JayBazuzi/comparison-keywords

Keyword parsing