browserify: getting super tired of updating test/fixtures/secureBundling/lavamoat/node/policy.json

[boneskull]

This file changes almost every time package-lock.json changes. It fails the dirty check often. As @naugtur put it, it's a "commit detector."

1. We need to remove it from VCS.
2. If this policy file is used as a snapshot: It should not be used as a snapshot. We can make assertions about some subset of the policy, if necessary.
3. If this policy file is used only in the context of execution, then great--we don't need to do anything else except remove it from VCS.

I'll look at how exactly it's being consumed, then do 1 and (2 or 3).

[boneskull]

Ref: #987