[Extensibility Request] issue 30334: fix OnAfterCarryOutToReqWksh record order

[AleksandricMarko]

Summary

A subscriber to the OnAfterCarryOutToReqWksh integration event in codeunit 99000813 "Carry Out Action" needs to update the newly created target requisition line based on the source line it was copied from. The event's first parameter is passed by var precisely so subscribers can modify that record, but in version 28.1 the call was changed to pass the source line as the first argument and the target line by value, removing any way to persist changes to the target line. This regression blocks the reporter's process. This PR restores the previous argument order so the modifiable var parameter is once again the target requisition line.

Source issue repository: microsoft/ALAppExtensions; issue number: 30334

Changes Made

• Carry Out Action.CarryOutToReqWksh - restored the OnAfterCarryOutToReqWksh call to pass the target requisition line as the first (var) argument and the source line second, so subscribers can again modify and persist the target line; applied in both the W1 and NA layers.
• Mfg. Carry Out Action.OnAfterCarryOutToReqWksh - updated the subscriber to read the source worksheet identifiers from the second parameter to match the restored argument order, keeping planning routing line and capacity need propagation correct.

Fixes AB#641682

[github-actions]

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.

---

🔄 How to trigger a new status check:

1. 📤 Push a new commit to the PR branch, or
2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.