Adds new handling of assets in disk

With the persitent asset name feature introduced in IG3 the updating of assets
on disk stopped working. This commit fixes this by introducing a update asset
thread that triggers on cache clearings.
Hides metainfo in context meny based on InterPoint

The IP ToolTabsAndButtons.ContentToolbarContentPropertiesButton was used
to hide the metainfo option in  the tooblar but not in the context menu
for folders in Content tool. This has been fixed now so both menus use the
IP.
Updated componentController to solve favourite groupnames even with several names.
Fixed registry logic so it could distinguish between same name starts on assets.
Extended createUser-tag to take plain info instead of SystemUserVO only.
Better handling of favourite components
Removed alert-leftover
Removed debug
New option for createUserTag
Merge pull request #63 from stenbacka/metainfo-access-restriction

Hides metainfo in context meny based on InterPoint
Merge pull request #62 from stenbacka/asset-update-in-live

Adds new handling of assets in disk
Fixed so hidden pages are still available in nice-uri-lookup.
Implemented a big optimization of defeat caches logic.
Merge branch 'master' of github.com:bogeblad/infoglue
Fixed bugs in move asset logic and updating it's references.
Fixed sort order in content version history
Improved EOS-toolbar and incorporated approve/deny of publish-state pages/contents.
The mail functionality also contains direct links to review url:s.
New utility lib
Better test possibility in notifications. Also better graphic fixes.
Translated some forgotten labels in EOS
Fixed so cmsFullBaseURL is used in mails to users.
Fixed bug in EOS when using fckeditor 2
Fixed better approve/deny functionality inside content/pages. No need to use publishing tool anymore?
Also fixed height/width on ckeditor
Fix to reference controller missing some late references due to poor sort
Added more debug to import controller
New debug
Removed debug
New version number
Made a huge change on how Submit to publish works. Now one can use it as a pure notification system instead of pushing pages/contents into new publish-states.