Fix parsing of inline config after impact of PHP CS Fixer

Issue #31
Pull request #32

Make exception more informative

• Handle exceptions of registrar and entirely per file.
• Show real stack trace information of deeper exception

Releted to #30

Make more informative error of inline config parsing

• Write extended information about exception into STDERR.
• Don't stop whole process when cannot parse inline config of some TODO-comments.

Relates to #29

Inline config EXTRAS

Feature

Implemented inline config which can be added to the body of comment and permits supplement and override configuration of created issue.
I so called "Extras" - simple json-like format.

Restriction

It does not support quotation. So, all keys and values must be single word.
See related issue #26.

Fix preparing of summary and description of JIRA-issue

Unexpected symbols removed. See issue #20

Add support for marks of expiration

Make matching of comments more compatible with package "staabm/phpstan-todo-by". So, it supports matching of different issue keys and their places to avoid conflicts with marks of comment expiration.

Fix matching of leading symbols before tag

Permit before tag only:

• spaces
• slashes
• stars
• number signs

Extend JIRA issue configuration

New functionality

• Add default assignee into JIRA issue config
• Add priority config of JIRA issue
• Throw exception on invalid JIRA issue config

Fixes

• fix detection of prefixLength which leaded to extra spaces before injected issue key

Chore

• update documentation

Base implementation

Implemented:

• Detection of TODO-comments in php-files both single-line and multiple-line
• Posting TODO as issue in JIRA
• Injection of issue key (id) into TODO-comment.
• Make it configurable and extendable.

Known inconveniences:

• add extra spaces before key of issue when symbol semicolon is not used
• supports not all patterns of "auto-expired" comments from package "staabm/phpstan-todo-by"