✨ Description of Change

A concise summary of what is being changed. Please provide enough context for reviewers to be able to understand the change and why it is necessary. If the issue/ticket already provides enough information, you can put "See ticket" as the description.

Link to GitHub issue or Jira ticket: OBPIH-6625

Description:
In a regular outbound workflow when sending a shipment we have this exact code that triggers an event which handles sending appropriate notification to the user based on the provided shipmentStatus, the only problem was that the new implementation on the full outbound workflow was missing this event publish.

📷 Screenshots & Recordings (optional)

If this PR contains a UI change, consider adding one or more screenshots here or link to a screen recording to help reviewers visualize the change. Otherwise, you can remove this section.

📈 Test Plan

We require that all code changes come paired with a method of testing them. Please select which of the following testing approaches you've included with this change:

• Frontend automation tests (unit)
• Backend automation tests (unit, API, smoke)
• End-to-end tests (Playwright)
• Manual tests (please describe below)
• Not Applicable

Description of test plan (if applicable):

✅ Quality Checks

Please confirm and check each of the following to ensure that your change conforms to the coding standards of the project:

• The pull request title is prefixed with the issue/ticket number (Ex: [OBS-123] for Jira, [#0000] for GitHub, or [OBS-123, OBPIH-123] if there are multiple), or with [N/A] if not applicable
• The pull request description has enough information for someone without context to be able to understand the change and why it is needed
• The change has tests that prove the issue is fixed / the feature works as intended