Issue #12: Fix line continuation on \r\n

Previously I had overloaded `SkipWhitespace` to implement line
continuation, since the PowerShell Language Specification calls it a
kind of whitespace. However, there wasn't a way to preview `\r\n` there -
you can only preview one character at a time. I wrote an extension to
Irony to allow 2-character preview, but it hasn't been incorporated in to
the stock Irony codebase.

It's undesriable to depend on a local extension to Irony, because then the
stock Irony Grammar Explorer won't work. Plus, it makes keeping in sync
with new versions of Irony that much harder.

Irony includes a `LineContinuationTerminal` that does most of the work for
you, it only needed a few parameters set to make it do the
right thing for the PowerShell language.

I also modified the definition of `escaped_character_pattern` because it
was eating the backtick as part of a `generic_token`, instead of leaving
it for line continuation - bad!
Issue #13: Allow newlines as separators in hash literals.

1. Allow `statement_terminator` instead of `;`, so newlines are allowed

2. Turn on `AllowTrailingDelimeter`, since that's important

3. This created a new Shift/Reduce error, but I think that's not going to
effect the semantics of the parse tree.
Merge pull request #73 from JayBazuzi/line-continuation

Line continuation and newlines in hash literals
Add missing protected constructor
Return default RunspaceConfiguration for RunspaceConfiguration.Create()
Implement RunspaceConfiguration.Cmdlets
report exception type

for slightly easier diagnosis at the command line.
Fix Issue #75 - Can't open Pash.sln in VS2010

Commit 8b9e9e2a74c70622ba082200d348b8c2cff947fb changed the signature in the solution to indicate VS2012. VS does this even though it doesn't need to, so we have to keep an eye on it whenever modifying the solution.
Merge pull request #76 from JayBazuzi/bug-75

Fix Issue #75 - VS2010 compatibility
IRONY: `SourceSpan.ToString()` for easier debugging.
Issue #35: Rename projects "Pash.*" -> "*"
Issue #35: Update assembly & namespace names to remove "Pash."
Issue #35: Rename project directories to remove "Pash."
Issue #35: Remove "Pash." from "TestHost\Pash.System.Management"
Fix casing of "FIleSystemTests"
Remove `System.Management.cd`

I don't know anyone who finds these class diagrams useful. I prefer to
read the code.
Fix casing of directory "FIleSystemTests"

(This is the git side of cf0b1fe3135fa5d261bae863d577b2189458d621)
Merge pull request #77 from JayBazuzi/issue-35-assembly-names

Fixed #35 - assembly names shouldn't say "Pash."
Issue #9 - Prohibit whitespace in member access / invocation.
REFACTOR: Extract Method on whitespace prohibition