update version and remove CCI triggers

[baentsch]

• Update release information following release
• Remove CCI triggers from projects no longer supporting CCI

• [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 think it should be possible to trigger a Github Action in a downstream repo using a similar approach. Even if the parent job is in CircleCI, it could make a REST API call to trigger a job in Github Actions as long as it has the relevant access tokens. Maybe something like this would help: https://dev.to/rikurouvila/how-to-trigger-a-github-action-with-an-htt-request-545