to release the new "couldn't find the middleware" messages

When verification fails, we already produce an error dialog at the end, with "please view the log tab" details.

As such, no need to use ERROR here.

Looping over extensions is fun, but there's actually a function to get us what
we need; so use that directly instead.

Also, use the correct method to go from a CRL_DIST_POINT* to the distribution
point URL.

When we check the CA certificate, the issuer certificate is the root
certificate, not the CA. Yes, that's slightly confusing.

The multiple certificate validation functions should be called depending
on which certificate we're trying to check. However, we accidentally had
some logic reversals here, which resulted in the wrong function being
called for a particular certificate, and as a result an incorrect
verification result.

Fix.

… win7, 8 and 8.1 in case of a dll not found error as this one is most often the one that is missing

This function is a CK_BOOL; without a return statement, undefined behavior
ensues.

…en pkcs is newer)

These get stored on the card as '7', '8', '9', or 'A' (yes, in ASCII,
not in hex). Since that's hardly readable, add a convertor so something
useful gets shown instead.

TODO: replace the current temporary strings by final strings from the
RRN.

…l official documents

The error message that appears when the middleware can not be found did
not account for the fact that older versions of the middleware did not
yet install the JSON metadata for the middleware. Confusion ensues.

Update the strings so they clarify that a bit.

…e value for day also has no time related meaning,so we display it as spaces)

http://www.ibz.rrn.fgov.be/fileadmin/user_upload/nl/rr/instructies/IT-lijst/IT101_Geboortedatum.pdf

Note: we change "2017" to "2014" as the oldest one. That's not because we're lying, but because we recreated the info.plist at some point, which caused the original year to get lost.