create deb package and retain as artifact

[baentsch]

In pursuit of open-quantum-safe/oqs-provider#94 this PR prepares (for) binary releases (to be added to release packages, for example).

The binary is intentionally created to

• only contain the standardized algorithms ("STD")
• only use OpenSSL3 APIs (so it can seamlessly be integrated to ´oqsprovider´)
• be built shared (such as to permit independent dpkg -i(installs))

Suggestions for other setups welcome. Suggestions where (else) to store the artifact also welcome (www.openquantumsafe.org?)

• [no] 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.)
• [no] 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 oqs-provider, OQS-OpenSSL, OQS-BoringSSL, and OQS-OpenSSH will also need to be ready for review and merge by the time this is merged.)

[dstebila]

I'm not familiar with this feature of Github. What does it mean to preserve it as an artifact? Is it turned into a release? Or is there some other place it's available?

[baentsch]

I'm not familiar with this feature of Github. What does it mean to preserve it as an artifact? Is it turned into a release? Or is there some other place it's available?

Github artifacts are documented here. They are retained (and can be downloaded) for some time after the build, e.g., if they "stood the test of time" to then be made (either manually or via specific code: download & store to some place) available wherever one sees fit (e.g., in binaries linked to releases). This PR does not contain such "automated deploy code": We'd first need to decide where to send it to -- and under which conditions.

[baentsch]

For further clarification: With open-quantum-safe/oqs-provider#196 and this PR landing, deployment of liboqs on an x64 Linux with OpenSSL3 present then simply consists of running dpkg -i liboqs-0.8.1-dev-Linux.deb. This step of course is not necessary if liboqs has already been integrated to & installed via the package management system of the distribution used.

Subsequent installation of oqsprovider then is simply dpkg -i oqs-provider-0.5.1-dev-Linux.deb. After this, one can operate openssl with all OQS alg combinations (again, assuming they have openssl >= 3.0 installed and activated oqsprovider). Again, dpkg -i would not be necessary any more if/when oqsprovider is integrated to the distribution's package management system.