### Issue before this commit:
When issuing a Delivery Guide for an "Itinerant issuer transfer CP", SUNAT rejects the document with error 3416 because the establishment code of the arrival point is being reported.

### Steps to reproduce the issue:
1. Download Stock, l10n_pe_edi_stock and l10n_pe_reports_stock
2. Create one contact setting a valid RUC
3. Go to settings and insert Credentials for Sunat Delivery Guide API
4. Create a new warehouse
5. Go to deliveries and create a new one with:
	1. Delivery Address: the contact you created
	2. Transport Type: Public Transport
	3. Reason for transfer: Itinerant issuer transfer CP
	4. Operator (in the PE EDI tab): any
6. Validate the delivery
7. Generate the delivery guide
8. There was an error communicating with the SUNAT service. Details: 400 Client Error: Bad Request for url: https://api-seguridad.sunat.gob.pe/v1/clientessol/test/oauth2/token/
9. If you download the generated XML, you will see that the node <cbc:AddressTypeCode> inside <cac:DeliveryAddress> is being generated with a default value of "0" but it should not be there

### Cause of the issue:
The UBL template automatically forces the <cbc:AddressTypeCode> node with a default value of "0" for any delivery address associated with a RUC (identification type 6). However, SUNAT's validation rules strictly forbid this node when the transfer reason is 18.

### Reason to introduce the fix:
Update the XML template to conditionally omit the <cbc:AddressTypeCode> tag inside <cac:DeliveryAddress> whenever the l10n_pe_edi_reason_for_transfer is '18'. This ensures compliance with SUNAT's validation rules and allows the successful generation of the delivery guide.

opw-6493067

Forward-Port-Of: odoo/enterprise#132991
Forward-Port-Of: odoo/enterprise#131431