This reverts commit c45c2295.

to get test passing again

~~drop the patch in DateTime._parse_args which cause DateTime to
support timezone naive dates~~
~~adjust __setstate__ to pickle the timezone naive flag~~

=> no we keep it the same patch as it was, without timezone
native support

adjust code relying on DateTime private attributes

adjust tests for new DateTime.__eq__ behavior (instances with
different timezones are different)

more testing, especially for various __setstate__ versions

introduce a context manager to change timezone in tests.

See merge request nexedi/erp5!1723

The changes from ae15e7e1 (accounting: show the context when
showing invalid bank accounts, 2022-12-21) were a regression because
with the previous behaviour, by just looking at the transactions,
users could see with the ??? that something was wrong with the bank
account. After these changes they had to open the select element.

This restore somehow the previous behaviour by displaying the label
with ??? marker, but since we have the label, we display the
label (bank account reference) instead of the value (the relative URL)

This was working only with Organisations

Fix small problems displaying bank accounts on accounting transactions and be more strict during validation:
 - bank account must be validated
 - bank account must belong to the section

The latter was a problem for scenarios like this:
 - create transaction for supplier 1 with supplier 1 bank account
 - clone transaction
 - change to supplier 2
the bank account remains as supplier 1 bank account, although it became an invoice from supplier 2.
The transaction could be validated as long as the bank account is not invalidated

See merge request nexedi/erp5!1713

See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type

The only check with accounting transactions regarding bank account
was that the bank account is not invalidated. This makes the
constraint more strict by checking that the bank account belongs to
the corresponding entity and also that the bank account is validated.

A few tests needed to be updated to validate the bank accounts. Also
a legacy sequence test has been removed because it is now covered by
normal tests.

The parameter is still named `organisation` for "API stability", but
this parameter can be a person.

This was already used by the fields on accounting transaction for
source/destination_payment and more or less working already, except
for the case where the person had a subordination to an organisation
member of the group, in that case instead of showing the bank accounts
from the person this was showing the bank accounts from the
organisation

On a transaction without section / mirror section, on the profile tab
all accouts where displayed

drop skip_invalidated_bank_accounts option, we are now using
base_category instead.

erp5_accounting, erp5_payment_mean: display currently selected Bank Account even if it is invalidated.

no need to validate them in the test

We had nexedi/erp5@a6b588e7 but this was only solving the case of a trailing ;

See merge request nexedi/erp5!1710

See nexedi/erp5@0c2dd107

Coding crime.

See nexedi/erp5@cbb3b35b

`python` command doesn't exist anymore in most recent distribution and
our PASS (theia), but python3 has been available for years now.

See merge request nexedi/erp5!1719

https://lab.nexedi.com/nexedi/erp5/blob/bb7d107124e96a6176f56226d3093d8845c3949d/product/Formulator/Form.py#L228

See merge request nexedi/erp5!1718

context is actually a web section