Fix support for dynamic matchers

[pirj]

See rspec/rspec-collection_matchers#48

If a matcher supports dynamic arbitrary methods called on it, e.g. have_at_least(100).bucks, it would also consider a supports_value_expectations? call as a dynamic part.

Instead of calling supports_*? methods on a matcher, explicitly check if it responds to it.

Symmetrical change for main that suffers when rspec-rails 4.1.0.pre is used and rspec-expectations 3.11.0.pre is at #1294

[pirj]

Pretty weird, several builds failed with

Fetching gem metadata from https://rubygems.org/....
Retrying dependency api due to error (2/4): Bundler::HTTPError Net::HTTPBadGateway: I/O error

and

Retrying download gem from https://rubygems.org/ due to error (2/4): Gem::RemoteFetcher::FetchError bad response Gateway Error 502 (https://rubygems.org/gems/parallel-1.20.1.gem)

while https://status.rubygems.org/ reports no incidents. Re-running.
PS didn't help, some jobs still fail.

[JonRowe]

A shame but sure 😂