[FW][IMP] inventory: delivery orders and incoming shipments restructure

[fw-bot]

Tasks: #3205819, #3208499, #3208472, #3210922, #3189292, #3189335

Targets: 14.0, 15.0, & 16.0

This PR restructures the Delivery Orders and Incoming Shipments folders by consolidating both folders into a single Incoming Shipments & Delivery Orders folder and merges the following docs:

• delivery/inventory_flow.rst ➡️ shipments_deliveries/inventory_flow.rst
• delivery/one_step.rst & incoming/one_step.rst ➡️ shipments_deliveries/receipts_delivery_one_step.rst
• delivery/two_steps.rst & incoming/two_step.rst ➡️ shipments_deliveries/receipts_delivery_two_steps.rst
• delivery/three_steps.rst ➡️ shipments_deliveries/delivery_three_steps.rst
• incoming/three_steps.rst ➡️ shipments_deliveries/receipts_three_steps.rst

As well as moved two files from Delivery Orders to a more appropriate location for the file content Shipping Operations:

• delivery/label_type.rst ➡️ shipping/operation/label_type.rst
• delivery/dropshipping.rst ➡️ shipping/operation/dropshipping.rst

Here are images showing the old structure and the new structure created by this PR.

Redirects were added for all file moves and name changes.

Forward-Port-Of: #3762

[robodoo]

Pull request status dashboard.

[fw-bot]

@samueljlieber @StraubCreative cherrypicking of pull request #3762 failed.

stdout:

Auto-merging content/applications/inventory_and_mrp/inventory/management.rst
CONFLICT (content): Merge conflict in content/applications/inventory_and_mrp/inventory/management.rst

stderr:

02:24:47.950397 git.c:455               trace: built-in: git cherry-pick c91b7b377016c7bcdedb586dddf6e5aae3d8d4ed
error: could not apply c91b7b377... [IMP] inventory: delivery orders and incoming shipments restructure
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

[StraubCreative]

@samueljlieber can you take a look please?
After we should be able to continue the FWP which will generate the full chain.

Reminder not to fw-bot r+ the master branch we need to tag JCS on 16.0 branches 😉

[jcs-odoo]

I took the liberty to fix this one as it was a really small conflict :)

@robodoo r+