Support for Parser Files

[StartAutomating]

A Parser File Should represent a way to parse input.

Tentatively, it should support the following file patterns:

• .parser.ps1
• .irregular.parser.ps1

A parser would be "valid" under a few potential conditions:

• The input passes a [ValidateScript({})] requirement
• The file name, command name, or inputObject matches a [ValidatePattern()]

Parser files would be able to take pipelined input, weather or not a process block is present ( If process is present, a steppable pipeline should be used, if it is not, each pipelined object should be splatted to the file).

From this point on, a parser would be "on its own".

It would be the goal of a parser to take that input and turn it into objects or otherwise interpret it.

Parsers should not require Irregular, in the same way that .Regex.txt and .Regex.ps1 Do Not Require Irregular

Related to #177