Replace `pass` usage in `Result` with `passed`

[shrink]

#47 replaced the pass output with passed so from an end-user perspective, the interface makes sense now, however, pass is used internally and externally by Javascript assertions.

I'm not sure how to deal with this mistake in a backwards-compatible way given third-party packages could depend on this interface... however, I don't think anyone is using this Action yet with custom assertions so maybe I can get with fixing it in a backwards-incompatible way.

• Add Add version parameter to npm:// assertions #50 to v2