Reject command node promise on abortOnFailure.

[garg3133]

If a command results in an error with abortOnFailure set to true, the node promise of the command inside the test case still gets resolved instead of getting rejected, while the queue is anyway cleared because of abortOnFailure.

This leads to a situation where if we chain some more commands after this command in the test case, the test would get stuck (because the queue is emptied) and hence will abort successfully. But, if the await is directly used on the command, that await will resolve and the test will continue normally since the following commands will be added to the queue after the queue is cleared.

The command promise inside the test case should instead be rejected so that the test case throws an error and thus aborting itself instead of continuing normally.

TODO: Find out which commands it affects.

[github-actions]

Status

• ❌ No modified files found in the types directory.
  Please make sure to include types for any changes you have made. Thank you!.