Let tables handle arbitrary objects

Specifically to support a clean syntax for tables built from Hashes,
this commit enables you to use the normal clean `column` and `row`
syntax like this:

```ruby
table_for foo: 1, bar: 2 do
  column :foo
  column :bar
end
```

Note that `dom_id_for`, which `attributes_table_for` was already using
but `table_for` wasn't, is definied by Arbre.
fix: title_bar makeup - only direct child link gets rounded borders
fix: dropdown menu click preventDefault
remove stopPropagation
Can pass proc to filter label option
Merge pull request #2824 from SoftSwiss/filter_label

Can pass proc to filter label option
Merge pull request #2815 from sandrew/dropdown-js-prevent_default

Dropdown menu on click navigates to top of the page
test Ruby 2.1.0
so much for DRY code

Lots of view helper-related code by changing the behavior of
`call_method_or_proc_on`, so I had to revert it.

The plan is to combine `table_for` and `attributes_table_for` so they
use the same code, so at least we'll have less duplication because of
that.

Note that I changed the collection-detecting code to do literally what
we expect, instead of trying to class-detect every possible variation.
This was necessary to keep collection decorators working.
Merge pull request #2812 from seanlinsley/feature/1713-support_arbitrary_objects_for_tables

Let tables handle arbitrary objects
Fixing gittip badge
Merge pull request #2828 from BukhariH/GitTip

Fixing gittip badge
fix expect value in filter_form_builder_spec
Fix has_many form rendering with new_record: false

Fixes #2773
Merge pull request #2831 from shekibobo/2773-fix-has-many-new-record

Fix has_many form rendering with new_record: false
disallow Kaminari 0.15.0

this prevents users from running into #2537
use latest bundler so Travis works with Ruby 2.1.0
Merge pull request #2830 from YETI-switch/master

fix expect value in filter_form_builder_spec
provide a more robust fix to prevent filter conditions from being deleted

This was spurred on by #2832, and effectively replaces #2523.

TL;DR it was the filter form's problem, so the resource extension
shouldn't have been trying to compensate.
Merge pull request #2814 from sandrew/2813-resource-action_item-makeup-fix-for-dropdown_meny

Resource action_item makeup fix for dropdown_menu