Display the notification for missing tenprint cards on the 'add file' page for the submitter accounts

This will load the page with all submission, THEN make a ajax query to
get all the submissions that contains missing informations. This is done
in two steps to have a fast loading page.

The query takes ~800ms for 100 submissions with the query done on the
server side before the loading, and only 70ms when done without this
information but loaded via ajax after. Since the backend function is the
same, the total time is the same, but at least the homepage will load
for the user.

We shall refactor the backend sql query to have only one query done
against postgresql.

This will position the tooltip relative to the position of the
mouseenter-ed object, and not the position of the mouse. This will
improve the reliability of the placement for the tool tip since the
location of the div on the screen does not changes.

This allows to easily import the function to generate the markers,
instead of copy/paste the same div>svg tags.

This simplify the display of the tenprint cards by removing the
classification by type (front, back and nist files). The layout of the
images is hence simpler to do.

This will, at the moment, only check if the tenprint card contains at
least one segment. It not possible to know if all the segments are
correctly annotated on the tenprint card because some cards contains
the rolled finger and some don't, and it could be a palm-card or
finger-card, i.e 2/4 or 10/12/14 segments respectively.

This will add a tooltip for each of the marks, indicating to the user
the missing information in the database. The color orange is used when
some fields are not populated.

If the value is set to "{}", the information shall be considered null.
This situation can append when removing an information from the detail
page, a null object is send to the server and stored in the database.

This behaviour should also be patched on the backend part.

This may be related to the issues seen by users to configure the
account. This bug is only confirmed on Firefox on Mac.

The configuration error is a 500 due to a missing 'password' field in
the session, probably related to a clear of the session.

This clear of session only being done on the opening of the /config
page, it could be that Firefox reload the page or re-do a query in the
background, hence clearing the session.

This bug is not reproducible on Chromium nor Firefox on Linux.

Move all the files in the "templates/submission" folder.