this info is already in the forontend docs

chore(deps): update dependency karma to v6

See merge request dbp/apps/signature!14

Now that we check every file on start we can just compute the value
there and re-use it for future checks.

chore(deps): update dependency eslint-plugin-jsdoc to v31.0.3

See merge request dbp/apps/signature!12

qual-sig: Fix URL escaping when fetching the file

See merge request dbp/apps/signature!13

Existing signature warning

See merge request dbp/apps/signature!10

There was a workaround for deriving the filename from the source filename
because characters like '#' didn't make it through.

Turns out this was just a bug some lines above where encodeURIComponent()
wasn't used as it should.

Use encodeURIComponent() when constructing the URL and remove the
workaround.

In case we get a signed document pdf-as in the backend can't add a new
page because implementations like Adobe Reader don't allow adding pages
after a signature has been added when checking the integrity.

A newer pdf-as version will take this into account and in the "auto" mode
position the signature on the first page. Since this usually means that
content will be overlaid this isn't a good "auto" mode.

To avoid this we check if the document is already signed in the frontend,
and force the user to place the signature manually in that case.

chore(deps): update dependency eslint-plugin-jsdoc to v31

See merge request dbp/apps/signature!11

Fixed since Chrome 85+

Not every activity needs those file queuing things

Hide the FileReader API behind an asnyc function. This makes it
easier to await the result and is less racy.

The option moved in the latest version of the plugin

Add a funtion for guessing the signature count of a PDF file

See merge request dbp/apps/signature!9

We require the signature count in the future to force users to
do a manual positioning when there are already signatures in the file
since we can't add a new page for them.

This uses a simple regex, matching parts of the signatures we use (PAdES).

In case the result is wrong, worst case the user has to do extra work by positioning
or the auto positioning will put it at the top of the first page, which might not
be ideal, but the document is still signed either way.

chore(deps): update dependency @rollup/plugin-node-resolve to v11

See merge request dbp/apps/signature!5

chore(deps): update dependency @rollup/plugin-url to v6

See merge request dbp/apps/signature!6

chore(deps): update dependency @rollup/plugin-commonjs to v17

See merge request dbp/apps/signature!4

chore(deps): update all non-major dependencies

See merge request dbp/apps/signature!3

subsetted font package