feat(core-flows,fulfillment, fulfillment-manual, types): make fulfillment typings more specific

[fPolic]

What

• attempt to add more specific type definitions around fulfillment provider APIs

---

CLOSES CMRC-814
CLOSES CMRC-816
CLOSES CMRC-817

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 6, 2025 1:56pm

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			Jan 6, 2025 1:56pm
api-reference-v2	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 1:56pm
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 1:56pm
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 1:56pm
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 1:56pm
resources-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 6, 2025 1:56pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3b591f4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[olivermrbl]

Overall LGTM

nit: I think we shouldn't be mixing types from different domains, e.g. the fulfillment service interface should not use the OrderDTO, but instead a standalone type that happens to have properties shared with the other type.

[fPolic]

nit: I think we shouldn't be mixing types from different domains

@olivermrbl could you check the last commit