Use ArgumentParser instead of custom solution

[dannflor]

Currently the implementation of flags isn't conformant to standard convention vapor/docs#689. This and I assume several other issues could be alleviated by using ArgumentParser to format input for a Command.

[0xTim]

Using ArgumentParser is definitely the long term plan. When it was first released it was missing a few features we required to switch over but it might be in a better place now to do so

[gwynne]

#192 begins to address this.

[alemohamad]

@dannflor is this issue still needed?

[gwynne]

The plan at the current time is to replace (most of) ConsoleKit with ArgumentParser for Vapor 5, this issue effectively tracks that.

[Ernest0-Production]

@gwynne HI!
But after all, the Console-kit has such a convenient mechanism for working with a terminal as the Console (aka Terminal class), which is passed into the context of the command.

Will there be a separate project, or how will this be solved in conjunction with apple's swift argument parser?

[0xTim]

The current intention is that ConsoleKit will add a set on extensions on top of Argument Parser to add the extras that we currently have. Things like Commands will likely become completely deprecated