CI: Check unresolved symbols when compiled with OQS_DLOPEN_OPENSSL

[ueno]

As a follow-up of commit 64bceb3, this checks that the library artifacts don't contain any unresolved symbols from libcrypto.so when it is dynamically loaded.

• Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
• Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., oqs-provider will also need to be ready for review and merge by the time this is merged.)

[SWilson4]

Thanks for the follow-up PR! (And sorry to @baentsch for jumping the gun by merging the previous one before this test was added.)

[dstebila]

@praveksharma Is the build failure on cuPQC expected here?

[praveksharma]

@praveksharma Is the build failure on cuPQC expected here?

Yes, unfortunately, I think it has to do with CI image itself. Although, I'm not certain why test passed in #2044 but has been failing since. That particular test fails because CMake can't find the CUDA compiler, it shouldn't affect this PR.

[dstebila]

@praveksharma Is the build failure on cuPQC expected here?

Yes, unfortunately, I think it has to do with CI image itself. Although, I'm not certain why test passed in #2044 but has been failing since. That particular test fails because CMake can't find the CUDA compiler, it shouldn't affect this PR.

Okay, I'll merge this one now.