Followers of regular mail channels that have email sending turned off will no longer receive emails just because they follow the channel. This supports using channel follows for mobile push notifications without creating unwanted email, while direct mentions can still trigger email based on the user’s notification settings.

Do not send email to partner followers of non-mass-mailing channels.

When a partner follows a channel without "Send messages by email",
we expect the follower to not receive any email whatsoever.

This behaviour is required to implement mobile channel notifications
for some users without receiving them by email. Basically, users can
follow a channel to enable push notifications.

Note that a mention of the user in a non-mass-mailing channel still
sends an email to this user, in case the notification preferences are
set to "Handle by emails".

This update adjusts how the Mail app sends emails when no channel email address is involved. It helps make message delivery behavior more reliable and consistent for users relying on Odoo communications.

The Latin American invoicing flow now uses one consistent rule to determine which document types can be selected during invoice reversals. This reduces the chance of users choosing an invalid document type when Latin American documents are not in use.

Merges the computation of `l10n_latam_available_document_type_ids` and `l10n_latam_document_type_id` as they're really strongly related.

Note: not really sure about the conditions on the reversal: currently if there are no available types any type can be selected. Previously, *if* move_id had been modified *and* `l10n_latam_use_documents` was set (during the last modification of move_id) no type could be selected.

Task 2115472

Payment setup now applies tighter rules when choosing default payment tokens, ensuring tokens are only considered for suitable electronic payment methods. This helps prevent inappropriate payment options from being selected while preserving important settings such as capture mode and company filtering.

Task 2115472

New custom fields now use the expected copy behavior even when they are created outside the standard form, such as through Studio. This makes duplicated records more consistent and helps prevent unexpected missing values, while one-to-many fields keep their special non-copy behavior.

New fields created from `ir.model.fields` view form are copy=True by
default (copy=False in case of One2many) thanks to an onchange but
manually created fields were not (e.g. created from Studio)

Task: 2067885