I recently added a check inside the init_js_extensions method to check

whether resolver_match was present on the request. This can be missing

in the case where middleware decides to render a page instead of

delegating to the regular view (typically something like a 403). The

check I added wasn't quite correct, and could still fail in some cases.

This change updates it to address those cases.

Ran Review Board test suite where this was being hit.