flake8 is capable of running checks in parallel if we give it multiple files.

Sometimes after getting the captcha from anti-captcha.com the MyEdenred
website returns the error 'Invalid captcha response'. I have added a
condition not to raise a false wrongpass and try again the captcha

An AssertionError was raised even when there was no error found.

For new recipients, the first transfer needs to be validated with a
personal key card code and an app validation.

For certain contracts, text 'Veuillez contacter le Crédit Bailleur'
is present in lieu of the expected amount in the 'Montant restant dû'
column. We skip the account in that case.

Previously, the transactions were scraped by html, the transactions were not sorted
by the field date in the html, the transactions were sorted by timestampOperation,
a field which is not accessible in the html but accessible by JSON API,
the timestampOperations is the date at the time that the transaction has been debited.
The date in the html is the rdate.
With this fix, transactions will be properly sorted

The website can now ask us to validate the new recipient with an app
validation instead of sms. But we can force the sms validation.

The stock market were not correctly fecthed so we take the whole string
and manually remove 'Meilleure exécution' ?

Transfer to internal recipients require different data to be sent than a
transfer to an external recipients.

We found only cash market orders but deferred orders are theorically
possible.

Some rows are about refunds, they need to be filtered out.

change the regex of the login to avoid the space character because the
login is use in the url, and you can have a %20 in the url.

hasPositiveBalance seems to be the real indicator. ledgerBalance may or may not
have a sign, we must ignore it.

Some users are unauthorized to access life insurance.
This was raising an error cause the redirection to
the main website was not handled.

Multitype users (Pro and Par) might be needed to log as Pro using
old_login method.
But this will not work if they don't submit 'nuser' field.
Now Caisse d'Epargne sends an explicit error about it that we can
handle.

The password requirements have been updated.
Before, no more than 2 digit repeats.
Now you need at least 3 different numbers.

Transactions will lose their id but:
- nothing changes apart from that
- the id was a phony hash forged by the module itself, based on date, amount
  and label

This reverts commit fd0ebef2ca7ea013cf1cc620911b59836d2adee0.

When going on the recipients page, there sometimes are skippable action
needed messages that can be handled the same way it is done in
iter_accounts.

For some HSBC invests, there was a missing step to get the asset category.
The URL that is parsed to fetch it is on a different page.

On first login, we have to solve a CAPTCHA to login, and then swile gives an
access_token and a refresh_token.
But unlike previous code, on subsequent logins, we can reuse the same
access_token, rather than solving the CAPTCHA again.
And when the access_token expires, we can simply use the refresh_token to get
a fresh access_token, rather than solving another CAPTCHA.

By using OAuth2Mixin, we leverage its token management.

URL changed and it is now a JsonPage

API does not contain currency info...

It used to be done in old browser, but we try hard to eradicate it.

The BNP API routes changed, we need to adapt the requests to fetch SRRI,
recommended period, ISIN code, asset category and performances.

Now Pro browser uses same decoding needed for Par browser