openssl: add embed-bitcode if tools.apple:enable_bitcode is set

[kletoz]

Specify library name and version: openssl/1.x.x and openssl/3.x.x.

Add -fembed-bitcode to CFLAGS if tools.apple:enable_bitcode is configured; only for iOS and tvOS.

---

• I've read the contributing guidelines.
• 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.

[ghost]

I detected other pull requests that are modifying openssl/1.x.x recipe:

• openssl: Make debug build renaming optional #10939

This message is automatically generated by https://github.com/ericLemanissier/conan-center-conflicting-prs so don't hesitate to report issues/improvements there.

[Nekto89]

Doesn't watchOS also use this flag?

[kletoz]

Doesn't watchOS also use this flag?

Yes, it does. I'm not testing for watchOS, but as watchOS also uses this flag I will add it in the same case. Thanks!

[kletoz]

@SpaceIm, @prince-chrismc could you please recheck this PR. It's adding bitcode for Apple builds.

[conan-center-bot]

Conan v1 pipeline

Failure in build 7 (7fdfb428d36827505d53cde89a93a2a52bcc7928):

• openssl/1.1.1s@:
  Didn't run or was cancelled before finishing

• openssl/1.1.1q@:
  command 'git merge --no-ff 8ef97f6' failed with exit code 1:
  Auto-merging recipes/openssl/1.x.x/conanfile.py
  CONFLICT (content): Merge conflict in recipes/openssl/1.x.x/conanfile.py
  Automatic merge failed; fix conflicts and then commit the result.

• openssl/1.1.0l@:
  Didn't run or was cancelled before finishing

• openssl/1.1.1p@:
  Didn't run or was cancelled before finishing

• openssl/3.0.5@:
  Didn't run or was cancelled before finishing

• openssl/1.0.2u@:
  Didn't run or was cancelled before finishing

• openssl/3.0.7@:
  Didn't run or was cancelled before finishing

• openssl/3.0.4@:
  Didn't run or was cancelled before finishing

---

^{Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability.}