N°9455 - Feature removal - console screen behavior

[eespie]

Add a fast track button to the first setup screen to compile iTop with the current choices (only on update)

[greptile-apps]

Greptile Summary

This PR adds a fast-track path from the setup welcome screen into the update compatibility check. The main changes are:

• A “Keep current choices” setup form on update installations.
• Direct navigation from the welcome step to WizStepLandingBeforeAudit.
• Restoration of database, module, and extension choices for the skipped wizard path.
• Setup context tags added to wizard and ajax setup entry points.
• A new wizard pre-form display hook.

Confidence Score: 3/5

This should be fixed before merging.

• The fast-track path skips part of the normal module-choice finalization.

• Removed extensions can be lost before compatibility audit and cleanup.

• The symlink setting can be changed silently during the fast-track audit compile.

• setup/wizardsteps/WizStepLandingBeforeAudit.php

Important Files Changed

Filename	Overview
setup/wizardsteps/WizStepLandingBeforeAudit.php	Adds the fast-track state reconstruction, but misses some parameters normally produced by module-choice finalization.
setup/wizardsteps/WizStepWelcome.php	Creates the setup token earlier and renders the update-only fast-track form.

Comments Outside Diff (1)

1. setup/wizardsteps/WizStepLandingBeforeAudit.php, line 24 (link)

   Symlink flag disabled

   On the fast-track form there is no use_symbolic_links checkbox field, so SaveParameter() stores the default from MFCompiler::UseSymbolicLinks() as a boolean. DataAuditSequencer later enables symlinks only when the parameter is exactly the string "on", so an existing true symlink setting is silently turned off for the compatibility compile. That makes the fast-track audit compile with copied files instead of the current symlink behavior.

_{Reviews (1): Last reviewed commit: "Setup fast track (keep current options)" | Re-trigger Greptile}

[greptile-apps]

Extension diff missing

When the fast-track path is used, this branch only restores selected_extensions and selected_modules from the current database. It skips the normal GetAddedAndRemovedExtensions() finalization, so downstream audit and cleanup forms receive removed_extensions as the default empty list. If an installed extension is no longer present or should be treated as removed during the update, the compatibility compile and feature-removal flow can run without the required removal set and miss cleanup work before the upgrade continues.