gdal/post_3.5.0: bump deps

[mayeut]

Specify library name and version: gdal/post_3.5.0

close #18592

---

• 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.

[ghost]

I detected other pull requests that are modifying gdal/post_3.5.0 recipe:

• migrate gdal to conan v2 #19041
• gdal: fix build when with_libdeflate=True or when with_cryptopp=True and cryptopp is shared, bump deps #18592
• [gdal] add version 3.7.0 #18027
• gdal: Add support for spatialite and rasterlite2, update to 3.6.2 #16461

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

[mayeut]

blocked on #18501 to bump libtiff in libgeotiff

[github-actions]

Hooks produced the following warnings for commit ffd5bce

gdal/3.5.2

post_package(): WARN: [APPLE RELOCATABLE SHARED LIBS (KB-H077)] install_name dir of these shared libs is not @rpath: libgdal.31.dylib, libgdal.31.0.2.dylib, libgdal.dylib

gdal/3.5.1

post_package(): WARN: [APPLE RELOCATABLE SHARED LIBS (KB-H077)] install_name dir of these shared libs is not @rpath: libgdal.31.dylib, libgdal.dylib, libgdal.31.0.1.dylib

[mayeut]

@czoido, in the absence of @RubenRBS, can you also o review this one please ?
This is still in an effort to drop old versions of libwebp in #18416

[mayeut]

closing / reopening to trigger a new build

[mayeut]

closing / reopening to trigger a new build

[mayeut]

There's something that seems very wrong with Jenkins CI since its update the other day.
Every re-trigger ends with a new error, the build number/id overlaps with previous builds.

closing / reopening to trigger a new build

[mayeut]

closing / reopening to trigger a new build

[AndreyMlashkin]

I have cherry-picked your commits into mine PR

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 7 (d18b2aeae073870c21faa01bf12bdbbeb1439a81):

• gdal/3.5.1@:
  All packages built successfully! (All logs)

• gdal/3.5.2@:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ❌

Note: Conan v2 builds may be required once they are on the v2 ready list

The v2 pipeline failed. Please, review the errors and note this will be required for pull requests to be merged in the near future.

See details:

Failure in build 6 (d18b2aeae073870c21faa01bf12bdbbeb1439a81):

• gdal/3.5.2@:
  Error running command conan export --name gdal --version 3.5.2 recipes/gdal/post_3.5.0/conanfile.py:

  ======== Exporting recipe to the cache ========
  ERROR: Error loading conanfile at '/home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py': Unable to load conanfile in /home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py
    File "<frozen importlib._bootstrap_external>", line 728, in exec_module
    File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
    File "/home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py", line 5, in <module>
      from conans import CMake
  ImportError: cannot import name 'CMake' from 'conans' (/opt/pyenv/versions/3.7.13/lib/python3.7/site-packages/conans/__init__.py)
  

• gdal/3.5.1@:
  Error running command conan export --name gdal --version 3.5.1 recipes/gdal/post_3.5.0/conanfile.py:

  ======== Exporting recipe to the cache ========
  ERROR: Error loading conanfile at '/home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py': Unable to load conanfile in /home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py
    File "<frozen importlib._bootstrap_external>", line 728, in exec_module
    File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
    File "/home/conan/w/prod-v2_cci_PR-18499/recipes/gdal/post_3.5.0/conanfile.py", line 5, in <module>
      from conans import CMake
  ImportError: cannot import name 'CMake' from 'conans' (/opt/pyenv/versions/3.7.13/lib/python3.7/site-packages/conans/__init__.py)
  

---

^{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.}