Fix broken circleci job for macOS

[johnma14]

This PR updates the openssl version to be installed for testing macOS builds

The circleci config file currently points to openssl@3.1 to install openssl for macOS. This change was made as part of the following PR, where previously openssl@3 pointed to openssl v3.0.x which was causing errors trying to build oqs-provider. So the change was made to specify openssl@3.1. OpenSSL v3.2 was released last week and the circleci jobs for macOS started failing since openssl@3.1 is no longer available to install using homebrew. Instead the following are the options: openssl@3 (which points to the current stable version, v3.2), openssl@3.0 and openssl@1.1.

Changes made in this PR include:

• pointing the openssl version back to openssl@3 since it now points to the latest 3.2
• a small doc change to the CONTRIBUTING doc to update the circleci command to run a specific job locally. (This command no longer accepts the --job option)

[baentsch]

Conceptually the update looks good (except for the single comment just made). But why are there so many CI tasks failing currently?

[ghost]

LGTM too.
CI jobs are failing because a documentation file is not matching a generated file… looks weird to me

[baentsch]

looks weird to me

Actually, pretty unacceptable: The difference is in HQC: It seems like oqsprovider picked up the new HQC version -- without updated code points. My mistake (to not have been online :) as the merge of open-quantum-safe/liboqs#1585 should (must) have led to a code-point-updating PR in oqsprovider (fyi @SWilson4 @dstebila to help implement the things we write in liboqs PR: Pretty much at the time of merging such algorithm changes we ought to have downstream PRs available). #306 created to fix.

[johnma14]

@baentsch @thb-sb Thank you for figuring out the failing test issue. I was having a hard time figuring that out. Regarding the doc change in this PR, I can remove that but I found that while working on this and trying to do a local CI build. I have the latest version of CircleCI installed (which is v0.1.29314) and that doesn't have the --log option for circleci local execute command.

[baentsch]

that doesn't have the --log option for circleci local execute command

Ah, OK. Thanks for the explanation. And more importantly, it also doesn't have the --job option. What about just adding "[" "]" around --job then?

[baentsch]

Thank you for figuring out the failing test issue. I was having a hard time figuring that out.

Well, apologies for having you try to do this. This should not have happened to begin with.

[johnma14]

that doesn't have the --log option for circleci local execute command

Ah, OK. Thanks for the explanation. And more importantly, it also doesn't have the --job option. What about just adding "[" "]" around --job then?

Yes, that makes sense. Will do that. Thanks @baentsch

[johnma14]

Thank you for figuring out the failing test issue. I was having a hard time figuring that out.

Well, apologies for having you try to do this. This should not have happened to begin with.

No worries, its always good learning.

[SWilson4]

(fyi @SWilson4 @dstebila to help implement the things we write in liboqs PR: Pretty much at the time of merging such algorithm changes we ought to have downstream PRs available).

Noted, will do in the future. (In the near future, hopefully, for Falcon.)

[baentsch]

Please rebase to latest main and CI should turn green.

[ghost]

Thank you @johnma14 !