Relax type constraints on assertEquals method signature

[olafurpg]

Currently, the following expression fails to compile assertEquals(Some(1), Option(1)) while assertEquals(Option(1), Some(1)) compiles. The compile error message is also cryptic. This issue is about relaxing the type constraints on the method signature to allow more flexible ordering of parameters and have less cryptic compile errors.

[valencik]

This was completed in #521

All of the following now compile in v1.0.0 milestones:

assertEquals(Option(1), Some(1))
assertEquals(Some(1), Option(1))
assertEquals(Option(1), Option(1))