poco: conan v2 support

[SpaceIm]

Specify library name and version: lib/1.0

This is also a good place to share with all of us why you are submitting this PR (specially if it is a new addition to ConanCenter): is it a dependency of other libraries you want to package? Are you the author of the library? Thanks!

---

• I've read the guidelines for contributing.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the conan-center hook activated.

[conan-center-bot]

All green in build 6 (8a4558aefd724b7c93705eaf5a40e636a744c45f):

• poco/1.12.1@:
  All packages built successfully! (All logs)

• poco/1.11.2@:
  All packages built successfully! (All logs)

• poco/1.12.0@:
  All packages built successfully! (All logs)

• poco/1.12.2@:
  All packages built successfully! (All logs)

• poco/1.11.3@:
  All packages built successfully! (All logs)

• poco/1.11.0@:
  All packages built successfully! (All logs)

• poco/1.10.1@:
  All packages built successfully! (All logs)

• poco/1.10.0@:
  All packages built successfully! (All logs)

• poco/1.11.1@:
  All packages built successfully! (All logs)

• poco/1.8.1@:
  All packages built successfully! (All logs)

• poco/1.9.3@:
  All packages built successfully! (All logs)

• poco/1.9.4@:
  All packages built successfully! (All logs)

[uilianries]

LGTM

[db4]

This PR breaks compatibility with opessl/1.1.1n. Is this expected?

[SpaceIm]

You can open an issue, but I don't understand what you mean by breaking compatibility with openssl/1.1.1n

[db4]

I don't understand what you mean by breaking compatibility with openssl/1.1.1n

Trying to use poco/1.12.2 with openssl/1.1.1n. Poco build fails:

...
-- Building: Encodings
-- Building: XML
-- Building: JSON
-- Building: Util
-- Building: Net
-- Building: MongoDB
-- Building: Redis
-- Building: JWT
-- Building: Data
-- Building: ActiveRecord
-- Building: Zip
-- Configuring done
CMake Error at JWT/CMakeLists.txt:24 (target_link_libraries):
  Target "JWT" links to:

    Poco::Crypto

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

poco/1.12.2@#a9ba7f0cfd6d672139d7f0f50f64bce4 works as expected

[SpaceIm]

1/ Since #11663, openssl/1.1.1n recipe is not maintained anymore.
2/ This present PR of poco needs this fix in openssl recipe: #12838. But due to 1/, openssl/1.1.1n recipe doesn't have this fix.

[db4]

@SpaceIm thanks for looking into this. No, I don't need a specific version of openssl, upgrading to the latest version is OK