* Rename `check_execution_status_failure()` method to
  `assert_execution_status_failure()`;
* `assert_execution_status_failure()`: accept panic message as an arg.
* Explicitly specify the panic message for each
  `assert_execution_status_failure()` if the promise didn't fail with
  the provided error message.

* Usually the converted to string has either of following two messages formats:
  "Action #0: Smart contract panicked: ERR_MSG [src/some_file.rs:LINE_NUMBER:COLUMN_NUMBER]"
  "right: 'MISMATCHED_DATA': ERR_MSG [src/some_file.rs:LINE_NUMBER:COLUMN_NUMBER]"
  So the ": ERR_MSG [" pattern should catch all invariants of error,
  even if one of the errors message is a subset of another one
  (e.g. `ERR_MSG_FAILED` is a subset of `ERR_MSG_FAILED_FOO`).