Explicitly use Chef::Provider::Service::Debian on Debian/Ubuntu #150

The next version of Chef will use Chef::Provider::Service::Upstart by
default in Ubuntu 13.10+ [Changelog], [CHEF-5276]), because Ubuntu
stopped shipping compatibility links in /etc/init.d/ [bug], [wiki].

[Changelog] https://github.com/opscode/chef/blob/master/CHANGELOG.md
[CHEF-5276] https://tickets.opscode.com/browse/CHEF-5276
[bug]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1311810/comments/4
[wiki] https://wiki.ubuntu.com/UpstartCompatibleInitScripts
Itemize changes since last release for upcoming release
bump release version
Merge pull request #151 from srenatus/next_chef_upstart

Explicitly use Chef::Provider::Service::Debian on Debian/Ubuntu for now.
Adding Upstart service provider support is tracked as #189
added log message to indicate mod_python is not supported in apache2.4 on the rhel and fedora platforms(in our test cookbook). skips the rest of the test mod_python recipe
#151 Force the debian service provider to avoid issues on trusty, etc.
Added initial fixture for opensuse 11.1
Merge master, update docs
#194 #193 MaxClients and MaxRequestsPerChild clean up
README attribute clean up
fixing suse conf file name
minor change - {} to ()
Merge branch 'COOK-3900' of https://github.com/onehealth-cookbooks/apache2 into COOK-3900
rubocop cleanup
added more notes to the CHANGELOG.md
remove aspiration
make those tests pass!
Add cgibin_dir and docroot_dir to fedora platform fixtures
Lower default prefork serverlimit and maxrequestworkers to avoid test failure on fedora 20
updating changelog to be more clear about conf changes