Issue: Tags are Lost After Upgrade

Since cross-content-type tags are supported in vBulletin 4, we can simply duplicate the entries from the old threads for the wiki content-type. For vBulletin 3, thread tags are only for threads, so without reinventing the wheel, we can store the old tags in a dormant table so they are at least not lost. If the forum is upgraded to a vB4 or 5 which supports tags in other content types, they would become available again. If the wiki is imported to another forum that supports tags natively, likewise this table would be imported properly; otherwise the dormant data would be imported.

Maybe in a few releases we can focus on creating a tagging solution for forums that don't have one in the core software. For now the focus should at least be preventing the data loss of existing tags before VaultWiki 3 and 4.

Added a step to the upgrade script to attempt to find tags that were overlooked during the upgrade to Alpha 1.
Tags are manageable under vB4, since there is built-in support for multiple content-types. Tags are hidden but not lost in other platforms and versions.

Still need to add a dedicated VW3 importer step.
Also need to add support to the page DM for auto-tags and automatically adding categories as tags.

Importer steps complete.

Marking this as complete. The original issue of data loss has been corrected. Providing a fully-fledged tagging feature (referring to my mention of auto-tagging) is not the focus of this report.