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