Resolves: bug 252190
    Bug Description: 7.1 to 8.0 Migration Bug
    Reviewed by: nhosoi (Thanks!)
    Fix Description: Lots of issues
    1) Instead of using Net::Domain::hostname() for the hostname to use for server identifiers, we must use the leftmost component of the FullMachineName specified by the user.  One of the reasons is that hostname() and hostfqdn() can give different results such that hostname() is not the leftmost component of hostfqdn().  And we should just use whatever the user specifies.  This required several changes to the mapfiles, and a change to the maptable processing, to process the perl code to eval last, so that we can use token substitutions from the inf file and from hard coded strings.
    2) We need to add the global preferences stuff, during migration, in order for the console to function. We cannot rely on the migrated o=NetscapeRoot data because we have to make sure we specify the new jar files to use.  In addition, we need to migrate over any customizations that the user has made to these preferences.   This is handled by the new updateConsoleInfo function called during admin server migration.
    3) There were several resources for messages missing.  These have been added.
    4) With the new perl only ds instance creation code, there will actually be data in the database even though the server is not started.  This is what I believe was causing the error_removing_temp_db_files error.  So now, the code will only attempt to remove plain files, not directories that could be globbed.
    5) Use /opt/brand-ds for the old server root instead of /opt/pkgname.
    6) The migration log should use [Migration} not [Setup]
    7) migration should not report a fatal error upon success
    Platforms tested: RHEL4
    Flag Day: no
    Doc impact: no
    QA impact: should be covered by regular nightly and manual testing
    New Tests integrated into TET: none