More separation for each use case for CLI

[ewen-lbh]

Add one form for each use case in the usage pattern.

As docopt has some difficulties parsing nested optional positional arguments, I had to use ARGUMENTS... but I can still explain the different use cases in a different section, that will not be parsed by docopt:

Use cases: ideaseed is divided into 4 different use cases:
    Creating an issue
    $ ideaseed --issue [-T TITLE] [[OWNER/]REPO [PROJECT [COLUMN]]] IDEA [-@ ASSIGNEE...] [-# LABEL...] [-M MILESTONE] [options]
    
    Creating a project card
    $ ideaseed [[OWNER/]REPO [PROJECT [COLUMN]]] IDEA [options]
    
    Creating a project card on your GitHub profile
    # (replace "keyword" and "project" with actual values)
    $ ideaseed --user-keyword keyword --user-project project keyword [COLUMN] IDEA [options]
    # It is worth noting that --user-keyword and --user-project are values that you'll not change often,
    # so it's worth putting them in your alias and not having to type them out each time, for example:
    $ alias idea="ideaseed --user-keyword keyword --user-project project"
    $ idea keyword example
    
    Creating a Google Keep card
    $ ideaseed IDEA [-c COLOR] [-# LABEL...] [--pin] [options]

(This block of code asusmes #28, #42 and #43 have been resolved)

[ewen-lbh]

Closed by 0f86a87