botcha 7.x-1.1

This is the first stable release after the global refactoring completion (see #1804770: [META] Migrate to object-oriented architecture).
The main features are:

• OOP-style. The BOTCHA module is moved to OOP-architecture. It means that all "entities" that take part in BOTCHA functionality are turned into classes. That gives more flexibility to extend and freedom to modify.
• Like MVC-application. The module's internal structure has been changed completely. Now it looks like real MVC-application. It gives a chance to separate logic of the application and the layer of interoperability with Drupal platform - that means that the BOTCHA is going to become more version-independent. I hope in the future we would see a Drupal-version-independent BOTCHA module. It eases maintainership of the module.
• Fully test-covered. Tests covered almost every line of the code. Plus tests' structure has been unified - and now it is really simpler to maintain it. I hope you will enjoy.
• Helpful UI. Now UI lets you to turn on or off recipe applying per each form. It helps to avoid critical situation when one or more recipes doesn't work as you like: you should just turn them off and post an issue to Drupal.org - and your site would not be affected by any discomfort.
• Patch crowd funding model of self-financing. This release introduced a new model of self-financing the development of open source projects, which is implemented by PatchRanger service. The development will continue to be free - but if you want some feature faster or can't wait until bug is fixed, you should assign a bounty to the issue you are interested in. So do other users of this module. When the total sum of assignments for some issue becomes attractive for some developer (it could be one of the maintainers of the BOTCHA module also) - he provides a patch and gets paid (of course, if his patch makes the issue closed for at least 2 weeks). If you are ready for bounty assigning, you could do it here: BOTCHA module on PatchRanger.