When the user is not owner of an account, we have an error code while
trying to fetch the recipients of the account.

PFMs need to keep track of accounts, which is done using various generic
methods. However, complicated cases may occur on some sites, where no generic
method works, without harming other modules.

A new capability method is introduced to allow module-specific diff behavior.
Essentially, a diff consists in:
- matching accounts, pairs of new/old objects
- new accounts, that were not seen before and are known to be new
- obsolete accounts, that are known to have disappeared
- unknown accounts, which could simply not be matched, but may be mapped by
  another method or manually by a user

The password isn't encoded in base 64 anymore. All connections have been
set to wrongpass because we sent the password after encoding it.

It seems that the display slightly changed for euro funds investments:
now they display a 'percentage' in the 'Cours' column (which usually
contains the unitvalue or the original_unitvalue) and display the
purchased amount in the 'Quantité' column.
We must ignore these values because they do not correspond to the data
usually contained in these columns.

Some users have a different page on which they need to go to have the
list of their recipients.

Add theses 2 new attributes in order to be more explicite about transfer behavior:
* can_initiate_transfer_to_untrusted_beneficiary: the module can do transfer to untrusted beneficiary, for example:
        when module can't add new beneficiary without doing a transfer like n26
        or when module can do transfer to a beneficiary not listed in `iter_transfer_recipients` like for PSD2 modules
* can_initiate_transfer_without_emitter: the module can do transfer without giving it the emitter, for example:
        there is only, and will be only, one account like wallet
        or when the module can initiate transfer without emitter and the emitter is chosen afterwards like for PSD2 modules

The grid data is now handled seperatly between pro and ent.

When doing transfers to multiple new recipients in the same session, we
are asked to do an app validation but not a code.

ValueDate now returns a real "date" object, not a mere string

ValueDate returned date strings instead of date objects. Use strings only
for serialization/deserialization, but otherwise use a real date object.
Also, the implementation was inefficient as it reparsed the same string
multiple times.

before the password was only numbers, now it's alpha-numeric

Sometimes the URL is slightly different, we must handle '_jcr_' and
'jcr:'

It's not an optional or costly dependency.

Though a BOM makes no sense in UTF-8, some sites insisting on sending one
with JSON data... Drop it then, as standard "json" module fails when it
is present anyway.

This feature does not modify the API of BrowserSelenium.
To use a remote driver, a config Value 'remote_driver_url'
must be set. If this value is not set the previous behavior
is used, instantiating a local web driver.

The remote driver capabilites are built according to the module
configuration.

When switching to regular imports, ItemElementFromAbstractPage will become
obsolete. However, they will not be removed immediately, but they will be
reimplemented to be compatible with the new system. But the reimplementation
works at import-time, not at exec-time, and it's not possible to access params
defined in outer scopes at import-time. So, we make sure the attributes are
explicitly defined, not implicitly.

Quantity and validity date are not always available.

like the commit 4a2987a9727756baf57a3934fb502e14a94be533
In PSD2, the account id is the "identifiantPrestation" when the account id is "codeGuichet+numeroCompte" in website
and the transfer_check_account_id will be False because of that

In this case, we just need to check the "codeGuichet+numeroCompte" part in the "identifiantPrestation".

Fixing some issues introduced by fetching accounts on the wealth
accounts page, and some others:
- error 500 while going on the new page,
- a json field that needs to be optional,
- a fix for the matching of accounts from the synthesis and wealth pages.

in order to also retrieve recipient for PSD2 accounts.
In PSD2, the account id is the "identifiantPrestation"
when the account id is "codeGuichet+numeroCompte" in website

It makes sense to have it in bank caps too.

This new type will be used for all investment in real state such as
SCPI, OPCI, SCI...