Fix for the pkcs11/crypto tests

[mike-sul]

• Split the P11 engine config into two parts, the one that is really belongs to the engine, and the second that belongs to the key manager. The first part is static and is/should be the same across tests in a single test suite. The second part is modifiable, each test can specify its own values.

• Make the P11 engine singleton for a test suite. The openssl engine cannot be loaded/initialized twice withing the same process, therefore each test cannot have its own instance of the P11 engine, it has to be a singleton within a system process.

[codecov-commenter]

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a7983c5). Click here to learn what that means. The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #68   +/-   ##
=========================================
  Coverage          ?   84.45%           
=========================================
  Files             ?      172           
  Lines             ?    12255           
  Branches          ?        0           
=========================================
  Hits              ?    10350           
  Misses            ?     1905           
  Partials          ?        0           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update a7983c5...5e6e4ae. Read the comment docs.

[cajun-rat]

Nice one @mike-sul !