[18.0][ADD] fieldservice_subcontracting

[edescalona]

@BinhexTeam

T22502

The module integrates Field Service with Purchase to support subcontracted Field Service Orders.

It allows companies to assign an FSO to a worker, resolve the subcontract vendor from that worker or its parent company, automatically create a draft Purchase Order for the subcontracted service, update received quantities from FSO timesheets, and navigate between the FSO and the related Purchase Order.

Main features:

• Mark vendor partners as subcontractors.
• Resolve the subcontract vendor from the assigned worker:
  • use the worker partner's parent company when it is marked as subcontractor;
  • otherwise, use the worker related partner when it is marked as subcontractor;
  • if neither is marked as subcontractor, treat the worker as internal and do not create a Purchase Order.
• Require subcontractor partners to be configured as vendors.
• Configure a subcontracting service product on Field Service order templates.
• Create draft Purchase Orders from configured Field Service stages.
• Set the Purchase Order Expected Arrival from the FSO Scheduled End.
• Keep the Purchase Order Expected Arrival synchronized when FSO planned dates change.
• Update Purchase Order received quantities from FSO timesheets.
• Add smart buttons to navigate between FSOs and Purchase Orders.
• Protect reassignment and cancellation flows when active subcontract Purchase Orders exist.
• Cancel draft vendor bills before cancelling related subcontract Purchase Orders.
• Prevent automatic PO cancellation when related vendor bills are already posted.

Typical workflow:

• Configure the subcontractor vendor partner and enable Is Subcontractor.
• For workers employed by a subcontractor company, set that company as the parent of the worker related partner.
• Configure the subcontracting service product on the Field Service template.
• Assign the server action that creates subcontract POs to the desired Field Service stage.
• Assign the server action that updates received quantities to the closing stage.
• Assign a worker to an FSO and move it through the configured stages.
• Review, confirm and bill the generated Purchase Order using the standard Purchase flow.

[max3903]

/ocabot merge nobump

[OCA-git-bot]

This PR looks fantastic, let's merge it!
Prepared branch 18.0-ocabot-merge-pr-1535-by-max3903-bump-nobump, awaiting test results.

[OCA-git-bot]

@max3903 The merge process could not be finalized, because command twine upload --disable-progress-bar --non-interactive --repository-url https://upload.pypi.org/legacy/ -u __token__ odoo_addon_fieldservice_subcontracting-18.0.1.0.0.2-py3-none-any.whl failed with output:

Uploading distributions to https://upload.pypi.org/legacy/
Uploading odoo_addon_fieldservice_subcontracting-18.0.1.0.0.2-py3-none-any.whl
�[33mWARNING �[0m Error during upload. Retry with the --verbose option for more details. 
�[31mERROR   �[0m HTTPError: 429 Too Many Requests from https://upload.pypi.org/legacy/  
         Too Many Requests