Changes to module_integrity_verifier.cc that allow the function VerifyModule

On greg's suggestion, incorporated this change into 
https://codereview.chromium.org/406043003/

============================================================
Changes to module_integrity_verifier.cc that allow the function VerifyModule
to return a list of functions that may have been modified (in addition to
whether or not the module is modified).

BUG=

[krstnmnlsn, 2014-08-01 22:02:17]

6pm on a friday is when you're supposed to send out cls right... 
Here's the modified-function reporting stuff.  I have spent far too much time
rearranging/refactoring this, so I figured I would get some input on it before I
went any farther with that.  Also this doesn't include the latest changes from
the first branch (https://codereview.chromium.org/406043003/) yet.

One thing is that I would really like to pull out chunks of what VerifyModule
does into helpers, but all the helpers I've tried would need too many
inputs/outputs to be worth it.  I could add even more fields to the state object
I've got there (ModuleVerificationState - name open to suggestions) and have
less parameters that way, thoughts?

Ignore the (almost non-existent) tests for now :)

[grt (UTC plus 2), 2014-08-01 23:28:33]

On 2014/08/01 22:02:17, krstnmnlsn wrote:
> 6pm on a friday is when you're supposed to send out cls right... 
> Here's the modified-function reporting stuff.  I have spent far too much time
> rearranging/refactoring this, so I figured I would get some input on it before
I
> went any farther with that.  Also this doesn't include the latest changes from
> the first branch (https://codereview.chromium.org/406043003/) yet.
> 
> One thing is that I would really like to pull out chunks of what VerifyModule
> does into helpers, but all the helpers I've tried would need too many
> inputs/outputs to be worth it.  I could add even more fields to the state
object
> I've got there (ModuleVerificationState - name open to suggestions) and have
> less parameters that way, thoughts?
> 
> Ignore the (almost non-existent) tests for now :)

Is this an evolution of the work in issue 406043003 that is meant to follow it,
or to replace it? If the latter, could you make this a new patch set in that
issue? If yes, try something like "git cl issue 406043003" and "git br -u
origin/master" so that you can upload this change into the other rietveld issue.