Extract rule name and options to separate collector

[vjik]

My suggestion:

1) Remove method RuleInterface::getName(). 2) Remove interface RuleWithOptionsInterface. 3) Remove RulesDumper. 4) Create new RulesConvertor that would can be configured for usage with custom rules also.

Benefits:

• more clear rule classes
• allows move all default values to rule handlers, that allow override default values globally.

[samdark]

1. As an author of the custom rule, what would be different for me to implement / use the rule?
2. What if I want to ship it in a Composer package?
3. As a rule user, what would be different for me?

[vjik]

1. As an author of the custom rule, what would be different for me to implement / use the rule?

Implementation:

• method RuleInterface::getName() need to implement only when user used convertation rules to array
• if options needed, then yet another class for convert rule to array will be required (also user can implement new interface in rule).

Usage:

• add ability to change converatation to array for any rule.

2. What if I want to ship it in a Composer package?

It can be configured via Yii Config or manually.

3. As a rule user, what would be different for me?

See 1.

[samdark]

I like the ability to configure it, but I don't think we need to separate this information, since it logically belongs to rule itself.

[vjik]

In some cases need ability to configure converter rule to array. For example date format in date rule. In this case need to use separate converter.