kickcat: add version v2.3-rc3

[trns1997]

Summary

Changes to recipe: kickcat/ v2.3-rc3

---

• Read the contributing guidelines
• Checked that this PR is not a duplicate: list of PRs by recipe
• Tested locally with at least one configuration using a recent version of Conan

[trns1997]

ping @leducp

[jcar87]

Out of curiosity - what is the release strategy for this library?
We don't tend to add pre-releases - find it a bit odd that every version after 1.0.0 seems to be a release candidate - are there actual releases?

[leducp]

Well, it depends on the POV, but this library is currently used by our medical device (exoskeleton) and is as such under really long verification and validation process.
We see releases as final version that follow all our internal criteria for critical softwares and it can takes months/years, and we do not 'release' intermediate rc if we cannot prove them under this processus. However, we do use release candidate as 'release with less proof' so yes, it is a release :)

[jcar87]

Does that mean that no version since October 2021 has actually passed this rigorous validation process?
Just trying to understand - when we include things in Conan Center, we assume they have wide use or there is wider interest in the community, and we tend to avoid including pre-release software.

[leducp]

I think it is just a naming convention that differ: we put in release candidate 'production ready code' and we put them in release when they are 'safety critical production ready'.
I understand that this naming scheme is not really communicative outside of the company... I can push an evolution in naming for our open source projects if you think it worth it, maybe something like x.y.z and x.y.z-safety? If you have insight for the naming they are welcomed as we don't have many outside perspective.