Handle telINSUF_FEE_P about xrpl.js

[wltsmrz]

The idea here is to resubmit transactions whose fees are insufficient. I understand the argument for doing this but I think it would be a bad idea without some indication in the client that transactions are being resubmitted.

[wltsmrz]

Actually I think a resubmission indication / ledger close indication in the client is overdue.

[sublimator]

I could easily be persuaded that resubmitting anything other than the first blob is a bad idea, and user interaction is required for resubmission of any altered blobs, yet I was under the impression that silently handling insufficient fees was always the intent?

[sublimator]

We're often silently producing different Fee's at the least, that's the primary reason for tracking each transactionID. Also, if we're going to abort, we need to be sure that we're aborting in response to the latest submission. If we're reporting a final result, we definitely want it to be final.

Maybe it would be nice to have the client authorize resubmission of any altered blobs. Hrmmm, yet the client isn't the only user of ripple-lib.

[wltsmrz]

telINSUF_FEE_P will now be resubmitted if Remote.local_signing is true (default)