Context Navigation

#39 closed defect (done)

The problem is:

When a central plugin is changed it's version number is changed as well
However plugins that just reference the new version of the plugin are not changed, thus their version number stays the same.
When we put the new version of the central plugin on the update-location the user will just download this update (only one where the version number has changed)
HL3 disables the old plugins because they reference an older version of the central plugin.

Thus we also need to publish new versions of the plugins that reference the new plugin even though the plugin hasn't changed at all.

One possible solution is to use an additional timestamp to signal that a newer version of an plugin is available.

Summary changed from Implement a more fine-granular way to recognize updates on the update-location that version-numbers to Implement a more fine-granular way to recognize updates on the update-location than version-numbers

Fixed with r91

Added class AssemblyBuildDateAttribute to PluginInfrastructure.
Changed all AssemblyInfo.frame files to include the attributed and use SubWCRev to automatically update the attribute with the current time of the build.
Adapted PluginInfrastructure and PluginManager to work with the new attribute (allow updates of plugins with same version but newer build time)