First view of updates report without cached release data reports bogus results for projects running HEAD

(Hard to come up with a concise summary of this bug in the title). ;)

The first time you view the available updates report when there's no cached available release data (e.g. you just saved the modules page and you visit the report before you click on one of the "check manually" links), cvs_deploy is in a sad state. When hook_system_info_alter() gets invoked, we don't have any cached data, and we therefore can't convert the version from HEAD into something else. Update status then fetches data, and compares the status, but it's going to think the version is not supported, since it doesn't know what version you're actually running and couldn't find any release information that matched what you've got (the release says the version is "7.x-1.x-dev", but it's looking for a version called "HEAD"). Lots of bogus results ensue. If you reload the page they go away. Yuck.

However, we can detect this edge case before we display it, and reload the page at that point, thanks to the miracle of hook_update_status_alter(). Patch coming soon, stay tuned.