Confluence must notify the user when the migration is complete to undo the memory and notification configuration

[petrenkonikita112263]

For the migration process, depending on the package size and its content, the user has to change the memory configuration (memory prerequisites) for XWiki. But at the end of migration, when all packages are processed. It's not good to have XWiki with high memory set-up for XWiki, and Migrator has to remind it.

Next, if migration was done during usage of old Confluence v1.7.3-

Tasks: #34: Remove notifications prerequisites

Before, this prerequisite was to disable notification. Still, after the migration, if the user doesn't enable the notification from the Xwiki setting file, the user can end up with a missing notification bell in the XWiki instance.

[raphj]

As discussed internally: this doesn't really applies anymore: requirements for running the migrator today are roughtly what is needed to use the wiki after the migration with the same content.

We don't require disabling notification anymore.

I would close this, users who used the old migrator will need to be guided through documentation and support, there's nothing we can really do for them in the Confluence Migrator's UI itself since they are unlikely to go back to it or even still have it installed.