Remove flow assert:

[seelabs]

Rounding in the payment engine is causing an assert to sometimes fire with "dust" amounts. This is causing issues when running debug builds of rippled. This issue will be addressed, but the assert is no longer serving its purpose.

Type of Change

• [ x] Bug fix (non-breaking change which fixes an issue)

[scottschurr]

I know it was hard to choose to do this, but I think this is a good choice. Having this assert fire was training me to be dismissive of asserts.

[Bronek]

I know it was hard to choose to do this, but I think this is a good choice. Having this assert fire was training me to be dismissive of asserts.

I think as long as we:

• know the reason for the assert fail and
• are confident the severity does not warrant it and
• reject the transaction anyway

... it's fine not to have it