Add shorthand `chain` syntax for custom matchers

The `chain` block in fluent matchers almost always just assigns its argument to an instance variable:

```ruby
RSpec::Matchers.define :be_bigger_than do |first|
  match do |actual|
    (actual > first) && (actual < @second)
  end

  chain :and_smaller_than do |second|
    @second = second
  end
end
```

Requiring a block is kind of overkill in this common case, and I get tired of reimplementing the exact same thing in every fluent matcher I define.

This pull request allows you to instead write:

```ruby
RSpec::Matchers.define :be_bigger_than do |first|
  match do |actual|
    (actual > first) && (actual < second)
  end

  chain :and_smaller_than, :second
end
```

Namely:

* you can just say `:second` instead of `do |second| @second = second end`; and
* as a bonus, since the DSL now knows a meaningful name for that remembered value, you can refer to it (e.g. in `match`) by saying `second` instead of `@second`.

I think this is an improvement. WDYT?
I think it only warns when readers are implicitly (?) made private by appearing after `private` in a class definition; if you explicitly make them private after the face (`private *attr_names`) it doesn’t complain.

I’m not sure what you mean by “even if it was ruby-private it would be API-public”, but I’m happy to leave the methods public if that’s the right thing to do.