Closes #173

The account table is present when no account is present, we need to add
condition to avoid research account in this case.

Closes: 27858@sibi

Sometimes the LCL website does not work properly and we randomly land on
the LoginPage while trying to get transactions:
AttributeError: 'LoginPage' object has no attribute 'get_operations'

I added an "if" to verify if we are on the login page and raise
BrowserUnavailable before calling "get_operations()" to prevent these
issues that are not always reproducible.

Closes: 16243@Sibi

There was a useless "break" after a "return" in a for loop of the class
_get_operations. This break will never be executer so I simply removed
it.

I had to divide by 100 the portfolio share we retrieved.

Page could be redirected to IndexPage if transfer is not allowed

TransferPage inherit from IndexPage so self.home.is_here() is true
Avoid this problem with check type of self.page

NSS seem to have different behaviors on different distros, e.g. Debian
and CentOS, and it also depends on the NSS version, which creates a
whole matrix of cases.
Try to force SQL database use for >=3.35 and default (probably DBM) for
versions <3.35.

NSS might still ask the infamous question:

    Enter Password or Pin for "NSS Certificate DB":

but deleting the old generated *.db files should solve it.

The encoding to the page seems to have changed and "PRÊT" appeared as
"PRêT" : the consequence was that Loans were not typed anymore and were
therefore scraped as regular accounts whereas the Loan page does not
have the same HTML structure.
Removing all the encodings of the module (incluging the subscriptions
part) worked since all pages are now in charset = UTF-8 on the website.

Closes: 27994@Sibi

it crash with ServerError 500,
now skip iter recipient to avoid crash

Before, the life insurance id were fetched from a request that does not
work anymore. In order to fetch the id we must use the new API that
contains account details as well as investments.
For life insurances that have no detail, the former code still works.

Closes: 7713@zendesk

 - Missing comma in list

Iban string retrieve is like this:
IBAN : EX6713281847025700290000236 Nom du Titulaire
or
IBAN : EX6713281847025700290000236 BIC / SWIFT

Sometimes the request to the old website returns a Server Error (500)
that crashes all BNP connections.
With this try/except , the connection to the old website will fail but
it will not prevent all the accounts from the new API to be scraped
correctly.

Closes: 7735@zendesk, 7863@zendesk, 27832@Sibi, 16333@Sibi, 27833@Sibi

Here we repair when label get numbers near the
original amount. Ex of transactions : "BLABLA 4x48 -193,00 DKK"

Closes: 27816@sibi

The market accounts were not scraped yet, the BNP website seems to have
changed recently.
This patch enables scraping of the market accounts.
The iter_investments method already worked as such, however the
pagination is not yet handled.
When there is only one account on the "invests" page, the checking and
the market account are fused into one account, the market balance is not
scraped, nor are the investments.
This patch enables both accounts to be visible with their respective
balances and the investments related to the market account.

Closes: 6827@zendesk

this times clients need to provides some documents

Before we did not handled when original amount were superior at 1000. Ex
of transactions : "BLABLA -7 350,00 RUB RU ST.PETERSBU".

Closes: 16732@zendesk

it seems that l4 and l5 are always present, retrieve them in raw
keep label unchanged

Account's id was created with the 4 first and last card's number. They was some duplicate,
so I Added the client name to the account id

Closes: 7284@zendesk 21370@sibi

wrongpass code 7 is "Vous ne pouvez pas encore vous connecter car votre code secret est en cours d'envoi"
action needed code 50 is "Votre mot de passe temporaire a expiré. Veuillez effectuer une nouvelle demande."

error code 207 is "Ce service est momentanément indisponible. Veuillez renouveler votre demande ultérieurement."

Closes: 27655@sibi 27257@sibi 27481@sibi 27483@sibi 27478@sibi

Some accounts dont handle debit card, so when retrieving the account
number attached, their isnt, cuasing the regex to crash. Added a
filter to check if the 'line' contains at least one digit. if not, we do
not get into retrieving the parent_id
Closes: 7346@zendesk

iban can be in lower case and is an alphanumeric string

For transaction ids, the (\d+_\d+) regex worked when the account id only
has digits but apparently some life insurances have letters in the ID.
The new regex, (\d+_[\dA-Z]+), handles both cases.

LCL just implemented a new API for the Life Insurance Space.
This patch handles navigation to the history and investments JSON pages
and the iteration of Transaction() and Investment() objects according to
their new website model.

Closes: 7713@zendesk

Closes: 12722@sibi

When running 'test' locally without encoding, I had an error caused by
the encoding.

Some life insurance account name was missing in the list

Closes: 16197@sibi

The new Linebourse's website uses new requests to an API that are implemented
in a brand new browser class (LinebourseAPIBrowser).

Caisse d'Epargne's connections still use the old Linebourse website,
that's why an additional class attribute stores the browser to use
(LINEBOURSE_BROWSER).

It is only used by Credit cooperatif's connections so far, so the
existing code has to be kept as such, using if-conditionals on the
current url to choose which requests to run.

Also, raise an ActionNeeded for the first connection (CGUs)

Sometimes, the website is randomly unavailable when we try to retrieve
iban_url's, causing a crash. A check for the expected page is added before
calling the method to get the iban url.

Some customers have a specific message in the iframe:
"Accès client - Sécurité renforcée
Cette opération sensible doit être validée par un code sécurité envoyé
par SMS ou serveur vocal."
Since we cannot bypass it by browsing the website or clicking on a
button are must raise ActionNeeded in this case.

This seems to concern customers who have not entered a phone number yet,
therefore I also had to correct the Regexp on the phone number in case
there is none for the CapProfile part.

Closes: 7432@zendesk

The sign of the original amount was not the same as the amount of the
transaction. Here we handle the positive and negative sign.

Closes: 16732@sibi

factorize cgu detection in one JsonPage
raise instance of BrowserIncorrectPassword and not class