Clean up the old code for the save-extension UX

[BLoe]

Related to #2557

There is now a lot of dead code in SaveExtensionWizard and useSavingWizard, since those will only ever be called for personal extensions, nothing with a recipe. We should delete the dead code, simplify these two as much as possible, and probably rename the hook to useExtensionSaver and can probably delete all of SaveExtensionWizard, and call SaveExtensionModal directly.

We should wait on this until after the new "create blueprint" feature is done, because this leftover code will be useful as a reference for that implementation.

[BLoe]

Blocked by #2932

[BLoe]

Split ElementWizard into EditorTabLayout and an implementation component, remove old code.

• ElementWizard
• AskQuestionModalButton

[BLoe]

This is definitely still worth looking into from a cleanup perspective, although some of the code in this area has changed/evolved since Apr2022

[github-actions[bot]]

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.

[github-actions[bot]]

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.

[github-actions[bot]]

This issue was closed because it has been stale for 7 days with no activity.