Version updater fixes

[maheshp]

• Version update check was enabled on new SPA pages.
• New Go version notifications are displayed on new SPA pages.
• Version check is skipped on DevelopmentServer
• Using route helper with _path rather than _url to fix One resource being loaded over HTTP #2350

[ketan]

See the production build does not package this file. So this will fail in production. Additionally even if you do package the file in production, you're likely not going to get the correct hash for version_updater in production. Post that, this will cause additional http requests to the server. Making for a less-than-ideal page load experience. Any possibility that we add this to each SPA?

We already require foundation.dropdownMenu and a few other friends for the navigation header on top, so don't mind putting that in the top level require itself

[ketan]

Additionally the check_go_updates? guard exists on old pages, but not in this one?

[maheshp]

I was looking at avoiding adding this script in each SPA, so was trying this option. Let me think bout and it we can look at the right way to do this.

check_go_updates? needs to be added, will add it.

[ketan]

Instead of stubbing m.request any possibility of directly using mock-ajax — makes for cleaner behaviorial tests. Here you're effectively testing what attributes you set on the deferred, aka — the internal implementation of m.request. If that changes, we'd have to re-write a whole bunch of tests, in addition to changing the actual code.

See this for reference.