Route Command Type #670

This should be a fairly straightforward command type.

It should be used to signal that a command will handle a route.

Which route the command will handle is determined by the [ValidatePattern] and [ValidateScript] attributes on the ScriptBlock (specifically, those that have an .ErrorMessage that starts with $Request)

Because the aspects related to command types should respect order, one could effectively route through several possibilities at fairly low cost (we'd checking the validations for every script, and only running what fits)

As with Parsers (#553), Routes should support multiple potential suffixes. That is:

Route,Routes,Router should all be considered Routes.

This command type should be extended for ease of integration:

• Route.Command.Validate should determine if a Route is Valid #695

PipeScript should also include a few "default" routes:

• Route.VersionInfo should return all loaded Versions #696
• Route.Uptime should return the uptime of the running process #697
• Route.Module should route requests to routes within a module #794