This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

Forward-Port-Of: odoo/enterprise#84135

The module behaves in an unexpected way:

- Tax is based on a customer's home address,
- To calculate tax a customer must be selected,
- Tax is calculated as if shipped from the warehouse selected on pos_warehouse_id

This could be useful in very obscure scenarios (B2B sales, traveling salesmen), but for those cases customers can already use our Avatax integration on sale orders.

We want this module to be useful for normal B2C POS sales. Taxes they charge are the same regardless of where the customer may live. This commit makes many changes:

- Stop requiring a customer to be selected,
- Always calculate local sales (from company location to company location) if the Avatax option is enabled on pos.config,
- Fix a bug where price_subtotal is not multiplied by quantity,
- Removes copy/pasted code from sale.order that serves no purpose,

This makes the module useful for companies that don't want to manually figure out what taxes to charge. This could be especially useful for companies with many shops in different locations.

A tour test was added to make sure the module keeps working. The test added before [1] was removed because it was redundant and less complete than the one included here.

This is deliberately not backported to Odoo 18 [2]. We keep the current behavior there.

[1] https://github.com/odoo/odoo/commit/3e94fe90ded58d498f0098cd9ed8679cbe500b8f

Closes odoo/enterprise#82779

task-4710463

This commit adds 4 attachments to the Latvian tax report
and an XML export for the tax report (including the attachments).

The attachments are the following
- PVN 1-I: domestic purchase / import
- PVN 1-II: EU purchase
- PVN 1-III: domestic sales / export
- PVN 2: EU sale

The attachments give more details for the tax report.
The lines of the attachments are "transactions"
A "transaction" is identified by the move and the transaction type or document type.
The transaction type is given via a tax tag (see community PR).
- PVN 1-I: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    independently of the move
  - 'V': All small transactions of a partner in case the total of all their small transactions reaches 150€
    - There is max 1 line per partner
  - 'T': All small transactions that are not grouped under some 'V' line
    - There is max 1 line like this; it has no partner information
- PVN 1-II: transaction type, move
  - Small transactions (< 150€) are aggregated separately under transaction types 'V' or 'T'
    (like PVN 1-I)
- PVN 1-III: document type, move and line in the main tax report
  - All transactions with (document) type 'X' are aggregated on a single line
  - Small transactions (< 150€) are aggregated separately under document types 'V' or 'T'
    (like PVN 1-I)
  - The line in the main tax report is ignored for 'X' and small transactions
- PVN 2: transaction type, move
  - No aggregation is performed here

Only account move lines that are tagged with a transaction type (1-I, 1-II, 2)
or a relevant tag for the main report (1-III) are shown in the reports.

The tags `Rep` and `C (car)` only take 40% and 50% respectively of the
base amounts. The tax amount is assumed to be split correctly.

task-4251184

This module has never worked in a stable release. It was broken two days after it was merged by the removal of replaceDataByKey [1].

On top of that, the module behaves in an unexpected way:

- Tax is based on a customer's home address,
- To calculate tax a customer must be selected,
- Tax is calculated as if shipped from the warehouse selected on pos_warehouse_id

This could be useful in very obscure scenarios (B2B sales, traveling salesmen), but for those cases customers can already use our Avatax integration on sale orders.

We want this module to be useful for normal B2C POS sales. Taxes they charge are the same regardless of where the customer may live. This commit makes many changes:

- Stop requiring a customer to be selected,
- Always calculate local sales (from company location to company location) if the Avatax option is enabled on pos.config,
- Fix a bug where price_subtotal is not multiplied by quantity,
- Removes copy/pasted code from sale.order that serves no purpose,

This makes the module useful for companies that don't want to manually figure out what taxes to charge. This could be especially useful for companies with many shops in different locations.

The module also doesn't handle the biggest challenge regarding external taxes: tax amounts Odoo calculates are not guaranteed to be the same as the ones returned by Avatax. There have been many fixes regarding this in other modules [2]. The summary of the situation is that the tax percentage returned by external tax calculators is only informational, and will not always be the "actual" tax percentage charged. Only the $ amount is authoritative. Differences can occur due to rounding, or due to automatically applied (partial) exemptions. The added test simulates this by deliberately misconfiguring a tax percentage amount.

Before this fix the POS would charge the wrong amounts in the above case. This commit adds a hacky mechanism that "freezes" tax amounts returned by Avatax and displays them as-is, bypassing the machinery that calculates taxes in JS. When a line is modified the amounts are unfrozen.

Note that in the case described above (Odoo taxes != Avatax taxes) the session closing entry won't be balanced. In this case the session must be force-closed with `pos.close.session.wizard`. It's not possible to fix this like we do for `l10n_br_edi_pos`, because we don't store the amounts per tax.

A tour test was added to make sure the module keeps working.

[1] https://github.com/odoo/odoo/commit/3e94fe90ded58d498f0098cd9ed8679cbe500b8f
[2] d941074434a0, a9783b107df2, b65308d67584

task-4676595