[Subcontracting] Added assisted setup guide for initial app configuration

[6CRIPT]

This PR adds an app-owned, three-step assisted setup guide for Subcontracting. The guide lets users review company defaults and navigate to the remaining configuration pages without relying on Manufacturing Setup during the installation session. Manufacturing Setup remains available through Manual Setup for later maintenance.

Also tests added.

Fixes AB#642233

[6CRIPT]

QUICK CONTEXT: The PR is about an assisted setup for the subcontracting extension.

The last copilot comment states basically that, once the Subcontracting setup is completed at least one time, if the user tries to run it again for some reason and then he leaves before finishing the setup, it will get a warning saying that the setup is not completed.

Copilot asks for the local variable SetupCompleted: Boolean; to initialize with the persisted value, so as soon as the extension is setup, the persisted value will store a TRUE.

What I think is the complete opposite, using ALWAYS a initial value of FALSE is better (in my opinion) because it warns the user the CURRENT process has not been completed (which is true). Therefore I would keep it.

However this is a personal opinion on the approach and actually both make sense and are correct. It depends of the perspective.

This is why I need third opinions. :)

NOTE: I did not found a clear pattern in other setups.

More context:

So we have the new set up:

With the 3 steps:

Once you press the "Finish" button, its properly set up.
But if you try to set it up again, and in the middle of the process you try to exit, you get the warning:

But the extension is properly installed. Therefore copilot suggest that this warning should go. I don't agree because I think that this warning should stay because it notifies the user that he is leaving without finishing the (new) set up, regardless of being one completed already.

[PredragMaricic]

No blocking findings. The assisted setup wizard is coherently registered, permissioned, instrumented, and covered by focused UI tests.

[PredragMaricic]

No blocking findings on the current head. The assisted setup object rename is consistent across registration, permissions, implementation, and tests, and removing the worksheet link keeps the final step focused on configuration.