[TASK] Add balance_change array to transaction response, computed from metadata

> 1. No semicolon at the end of a function declaration is a well-accepted standard.

No it isn't. A semicolon shouldn't be inserted after a function declaration automatically, but I don't think this is an assertion you can really prove

> Following it will potentially prevent confusion

Potential is practically zero. It reads clearer to insert semicolons after function declarations just as you would do to expressions

> 2. It looks like other ripple projects do not have semicolons at the end of function declarations.

You'll find that most projects other than ripple-lib don't have any style consistency

> 3. JSHint does provide good style enforcement for semicolons if you follow the standard. On the other hand, if we diverge from the standard, we get no enforcement at all. This means we can't enforce semicolons at the end of functions and we can't enforce not having semicolons at the end of if/for blocks, double semicolons at the end of lines, or any other random semicolons.

What is "the standard?" Semicolons are optional. JSHint helps a little, but it's quite lacking. You shouldn't take the default JSHint configuration as The Right Way to format a JavaScript program. If by "the standard" you mean the rules of ASI, JSHint doesn't enforce this by default.

> Given that the effort required is minimal (and probably less than the effort of changing all the other ripple projects for consistency) and we are going to have to be fixing a bunch of other jshint errors anyways, it seems that changing makes sense.

I'll just repeat myself then: Not all of the ripple-* projects need to be 100% consistent. If you think it's realistic to weed out all the number/string casting hacks, double/single quote inconsistencies, spacing inconsistencies, under_score/camelCase inconsistencies, function expression/declaration inconsistencies from ripple-client, I urge you to take a good look. Not only do we not *need* to enforce consistency across our projects, we haven't been from the beginning. It's not like enforcing semicolons after function declarations suddenly requires that we audit all Ripple codebases. But nice try :)

If you're going to actually clean up ripple-lib with JSHint, you can set asi: true and get rid of semicolons after the constructors and so on. It's a trivial task that has no practical significance.