Re-enable oqs-openssl111 interop testing

[baentsch]

As the conclusion arrived at in #32 (de-emphasizing oqs-openssl111 maintenance and support) has been reverted in yesterday's team meeting, this issue is to track tasks to re-activate interop testing between oqs-openssl111 and oqs-provider.

Implications:

• Interop test scripts need to be parameterized to
  o permit switching to different docker images (oqs-openssl111-curl had been used but has changed in the meantime to oqs-provider-curl)
  o permit switching off RFC data encoding testing as that is not implemented in oqs-openssl111 (or are you willing to add that also to oqs-openssl111, @bhess?)
• create and maintain separate docker images for oqs-provider and oqs-openssl111 operations (at least for curl) -- or completely revert upgrade curl and move to openssl3 oqs-demos#190 --opinions, @christianpaquin @dstebila ?

[baentsch]

@christianpaquin @dstebila For the avoidance of doubt, this issue is getting (at least my) attention only after open-quantum-safe/openssl#434 has been resolved.

[baentsch]

We agreed to terminate support of oqs-openssl111 and have significantly more functionality in oqs-provider, so closing as this is a truly pointless issue now.