Allow Rule to find Badge by `:badge_id`

I want to be able to edit Badge name and descriptions in my database, unfortunately by using a finder which relies on badge name I can’t easily modify badges without using a separate locked db column just to support the merit badge string name id.  Since IDs in relational databases aren’t modified it makes more sense to write the rules using attributes that aren’t going to be changing.  Merit badges have assigned IDs and already have a finder so I just modified the Rule class a little to support an added `:badge_id` attribute.

As it is a single attribute I set the finder to check for it first and use it for finding the badge if it is available, if not the finder falls back to `:find_by_name_and_level`

* Added `:badge_id` attribute to `Rule`
* Modified badge finder method to prefer `:badge_id` over `:badge_name` and `:level`
* Added test for Rule to support modified finder
* Added test for dummy app to support modified finder
* Documented use in badge rule template
* Documented use in README

The new use case would look something like this where `:badge_id` is the preferred finder attribute

```ruby
#config/initializers/merit.rb
Badge.all.each do |badge|
  Merit::Badge.create(
    id: badge.id,
    name: badge.name,
    level: 0,
    description: badge.description)
end

#app/models/merit/badge_rules.rb
# If it has 10 comments, grant commenter-10 badge, find badge by badge_id
grant_on 'comments#create', badge_id: 1, badge: 'commenter', level: 10 do |comment|
  comment.user.comments.count >= 10
end
```

> I want to push back on this a little. :badge is used in examples and tests all over the place and removing it from the readme we would be dropping what is the most referenced place for documentation.
>
> I could see an argument be made for adding a depreciation warning and then removing it from the API in a future version, but if it is going to be supported I think we should leave it in the README.

I understand, it makes sense to me. But current README doesn't show that we need only one, we could probably put a single item and connect them with "or". Thanks!