[ADD] account_move_tier_validation_purchase + _stock_landed_costs

[bosd]

What

Two new auto-installed bridge modules so vendor bills can still be matched to a Purchase Order and turned into a Landed Cost after reaching validation_status='validated' on account_move_tier_validation.

account_move_tier_validation_purchase

Depends on account_move_tier_validation + purchase. Adds the following fields to the tier-validation exception list:

• purchase_vendor_bill_id
• purchase_id
• invoice_vendor_bill_id
• invoice_origin
• invoice_line_ids
• line_ids

Use case: a purchasing user validates a draft bill; a finance user then attaches the matching PO via the Auto-complete from a past purchase order picker. Without this bridge, the picker is greyed out by base_tier_validation's view post-processing and the onchange-driven write of invoice_line_ids / invoice_origin would be refused by the post-validation write guard.

account_move_tier_validation_stock_landed_costs

Depends on account_move_tier_validation + stock_landed_costs. Adds:

• invoice_line_ids
• line_ids
• landed_costs_ids

Use case: a draft bill is validated; stock operations then mark one of the lines as a landed-cost line (which feeds _compute_landed_costs_visible and re-enables the Create Landed Costs button) and push the amount into stock valuation. Without this bridge the line is locked the moment validation lands and the user cannot reach the button.

Why two bridges instead of extending account_move_tier_validation

Adding the exceptions in account_move_tier_validation directly would force the base module to hard-depend on purchase and stock_landed_costs. The bridge pattern keeps the dependency edges clean: each bridge auto-installs only when both halves are present.

Tests

Each bridge ships a focused module-level test asserting the new fields are present in _get_validation_exceptions() -- the integration suite for the end-to-end flow (auto-complete a validated bill from a PO; mark a line as landed-cost on a validated bill and create the landed cost) lives in the customer project that requested this.

Notes

• Both modules are auto_install: True, so they activate transparently whenever their dependencies are met.
• No view or data changes -- only Python.

CC @LoisRForgeFlow