cpp-validator: add version 2.1.1

[toge]

Specify library name and version: cpp-validator/2.1.1

evgeniums/cpp-validator@v2.0.3...v2.1.1

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (9c7bdbd641daff0ebfcf56985d856e5bd3de9106):

• cpp-validator/2.1.1:
  All packages built successfully! (All logs)

• cpp-validator/2.0.3:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 1 (9c7bdbd641daff0ebfcf56985d856e5bd3de9106):

• cpp-validator/2.1.1:
  All packages built successfully! (All logs)

• cpp-validator/2.0.3:
  All packages built successfully! (All logs)

[AbrilRBS]

I'm checking https://github.com/evgeniums/cpp-validator/blob/main/docs/index.md#building-and-installation (To see if it makes sense to open a PR upstream to mention Conan support) - and noticed the bit about fmt backend needing a define to properly work. Isn't this something that should be reflected in the recipe? Both as an option, and in the package_info? wdyt @toge?

[memsharded]

I'm checking https://github.com/evgeniums/cpp-validator/blob/main/docs/index.md#building-and-installation (To see if it makes sense to open a PR upstream to mention Conan support) - and noticed the bit about fmt backend needing a define to properly work. Isn't this something that should be reflected in the recipe? Both as an option, and in the package_info? wdyt @toge?

Maybe the recipe can hardcode at the moment the fmt backend, as it is recommended and preferred, but the HATN_VALIDATOR_FMT macro seems it should be defined in consumers, not sure why the test_package is not failing.