Better Hamcrest matchers migration support #1
Description
Right now we only support a couple of Hamcrest matchers, but it would be nice to support more of them, in particular all the list matchers. The Hamcrest matchers migrations are a bit tedious, as to properly infer whether the migration is possible or not, one should be able to match whether the inputs of the matcher functions. Take these 2 examples:
assertThat(list, contains(element))
assertThat(list, contains(myMatcher))
In the former, we should be able to migrate to assertThat(list).contains(element), while in the latter we should fallback to the satisfies migration, as there's no way we can take that myMatcher and automatically convert it to assertj.
As a result of this task, we should have proper support for Hamcrest collections assertions