This module adds support for "codaclean" integration.
CODA files can be periodically (or on demand) fetched from codaclean
and imported into bank journals.
The module only connects to the IAP server.
The IAP side does the actual calls to codaclean (with a secret API key).

To use the module you have to create a connection to IAP / codaclean
and set up a bank journal:
- To manage the connection to IAP / codaclean go to
  Settings -> Accounting -> Codaclean -> Manage Connection
- To set up the bank journal you need to configure the following
  in the "Journal Entries" tab on the journal:
  - Put the IBAN in the "Bank Account Number" field
  - Select "Codaclean Synchronization" for the "Bank Feeds" field

Coda files will be automatically fetched 2 times per day via the
scheduled action called "Accounting: Sync Coda Files from Codaclean".
They can also be manually fetched by clicking "Fetch from Codaclean"
below the journal on the accounting dashboard (only available
when the journal and connection are setup correctly).

On an empty journal we start fetching from 1 year ago.
When the journal is not empty we start fetching after the last bank statement
/ bank statement line in the journal.

task-4844423

backport of commit 518ab9e

Forward-Port-Of: odoo/enterprise#96705
Forward-Port-Of: odoo/enterprise#95747

Issue:
When updating partner fields such as `email`, `name` and `phone` on the partner records,
the ticket fields are recomputed. During the recomputation, the `description` field is loaded into memory and with
many helpdesk tickets, this will cause a memory error.

Purpose of this PR:
To explicity fetch `partner_id` before computing partner fields on the helpdesk ticket.

Example:
With a partner record with 25,000 helpdesk tickets each with a description of varying text and images,
we hit the memory limit when trying to update the partner phone. With these changes, peak memory usage reached 271.4 MB.

Notes:
Originally wanted to avoid changing the field definition however this would require adding `with_context(prefetch_fields=False)`
to most of the compute methods on helpdesk ticket model.`with_context(prefetch_fields=False)` to most of the compute methods on helpdesk ticket model.

Memgraph and Stats before changes
<img width="1912" height="862" alt="memgraph_b4_changes" src="https://github.com/user-attachments/assets/f5e95a42-83c8-4250-bdf3-440740a9fb33" />
<img width="640" height="352" alt="stats_b4_changes" src="https://github.com/user-attachments/assets/a82ccd69-1359-4ba8-81a0-52aeace762db" />


opw-5069424

Forward-Port-Of: odoo/enterprise#96198

This is the backport of https://github.com/odoo/enterprise/pull/94111/commits/e379cf04cc1aa97d28d73566daadad193310ae9a

Issue:
In the list view of Journal Items, cash basis lines show a `move_name` of '/' event if the move is posted and has a name.

Steps to reproduce:
- Activate Cash Basis in the accounting settings
- Create a tax with "Tax Exigibility" set "Based on Payment"
- Set the "Cash Basis Transition Account" to "Current Assets"
- Activate reconciliation on "Current Assets"
- Create an invoice with this tax, confirm
- In the dashboard, click on Bank and new
- Set the name of the invoice as the label, and the amount of the invoice as amount
- Save & Close
- Go in Accounting > Transactions > Journal Items
- The lines created for the cah basis entry display '/' in the column "Journal Entry"

Cause:
This issue is linked to the order in which things are done in `_set_next_sequence`: the fields triggered by the sequence field are added in `self.env.transaction.tocompute` then the sequence is computed and assigned.

When `_set_next_sequence()` is called from [`_create_tax_cash_basis_moves()`](https://github.com/odoo/odoo/blob/849e4a87178d8c8588b75e3f7d9073d6a78326f9/addons/account/models/account_partial_reconcile.py#L649-L654) this order is problematic as `account.move.line.move_name` will be computed and removed from `self.env.transaction.tocompute`. So it will not be updated when the sequence is assigned in `account.move.name`. The callstack is something like this:
- `_set_next_sequence()` calls `_locked_increment()` to compute the sequence
- `_locked_increment()` calls `flush_recordset()` which will call `_recompute_recordset()` to recompute all fields
- `_compute_invoice_date_due()` needs the field `needed_terms` triggering `_compute_needed_terms()`
- `_compute_needed_terms()` needs `invoice_line_ids`
- the fetch on `account.move.line` is ordered by `move_name`
- So `_compute_related()` is triggered for `move_name` and `account.move.line.move_name` is removed from `self.env.transaction.tocompute` Then `_locked_increment()` returns the sequence, it gets assigned as the move name and `move_name` is never updated because it's not in `self.env.transaction.tocompute`.

This doesn't occur in other flows (like calling `action_post()`) because the value of `needed_terms` is read from the cache.

Solution:
Swap the order in which things are done in `_set_next_sequence()`: first compute and assign the sequence and then add the triggered fields in `self.env.transaction.tocompute` so that they are computed afterwards.

It seems more logic that way: we change the `_sequence_field` then mark all fields that will be impacted in `tocompute`.

Community PR - https://github.com/odoo/odoo/pull/230751

opw-4747878

Forward-Port-Of: odoo/enterprise#96721