thrift: add v0.20.0 and bump deps

[robomics]

Specify library name and version: thrift/all

---

• 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 (f971ff887c163782984956e7efcb58d69f90cb5b):

• thrift/0.18.1:
  All packages built successfully! (All logs)

• thrift/0.15.0:
  All packages built successfully! (All logs)

• thrift/0.14.2:
  All packages built successfully! (All logs)

• thrift/0.17.0:
  All packages built successfully! (All logs)

• thrift/0.20.0:
  All packages built successfully! (All logs)

• thrift/0.16.0:
  All packages built successfully! (All logs)

• thrift/0.14.1:
  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 (f971ff887c163782984956e7efcb58d69f90cb5b):

• thrift/0.14.2:
  All packages built successfully! (All logs)

• thrift/0.14.1:
  All packages built successfully! (All logs)

• thrift/0.17.0:
  All packages built successfully! (All logs)

• thrift/0.20.0:
  All packages built successfully! (All logs)

• thrift/0.16.0:
  All packages built successfully! (All logs)

• thrift/0.15.0:
  All packages built successfully! (All logs)

• thrift/0.18.1:
  All packages built successfully! (All logs)

[CJCombrink]

@robomics Thanks for the effort, you saved me from doing it :D

[CJCombrink]

@franramirez688 Thanks for the approval and merge

[jcar87]

pleaase be aware that version bumping like this introduces a conflict in opentelemetry-cpp.

I would advise against bumping versions unnecessarily unless there is a clear reason - for example, a new feature in boost that is required.

[CJCombrink]

@jcar87 I am very curious why adding a new thrift version have an affect on another package?
personally I think the packages should be independent of each other, except perhaps those that use ranges that the conan peaple have deemed can be ranged, like zlib and openssl when I last looked....

clear reason

0.20 is newer than 0.18.1, should be reason enough for a package manager

ps: thrift is pinned in opentelemetry-cpp, that am I missing?

self.requires("thrift/0.17.0")

Edit/update: probably the fact that opentelemetry-cpp specifies self.requires("boost/1.84.0"), perhaps it should get an override

self.requires("boost/1.84.0", override)

[CJCombrink]

I quickly looked at opentelemetry-cpp and it seems like it does not require boost, thrift requires boost. So perhaps the correct thing is to remove boost from the opentelemetry-cpp recipe?

(I am not familiar with opentelemetry-cpp)

[CJCombrink]

Ok finally it also seems that opentelemetry-cpp dropped the thrift requirement in version [1.10.0] 2023-07-11

[REMOVAL] Remove the jaeger exporter open-telemetry/opentelemetry-cpp#2031

So no need to worry about breaking it from the thrift side any more I guess.

Thus I stand on opentelemetry-cpp recipe must either get override on boost version or not specify it and use what thrift uses