Librasterlite2: bump deps

[ericLemanissier]

Specify library name and version: librasterlite2/*

closes #18456

---

• 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 librasterlite2/all recipe:

• librasterlite2/all: bump deps #18456
• librasterlite2: conan v2 support #16613

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

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (d3f429fa58754313af97ccf9525251d4f39de4ba):

• librasterlite2/1.1.0-beta1@:
  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 1 (d3f429fa58754313af97ccf9525251d4f39de4ba):

• librasterlite2/1.1.0-beta1@:
  Error running command conan export --name librasterlite2 --version 1.1.0-beta1 recipes/librasterlite2/all/conanfile.py:

  ======== Exporting recipe to the cache ========
  ERROR: Error loading conanfile at '/home/conan/w/prod-v2_cci_PR-18587/recipes/librasterlite2/all/conanfile.py': Unable to load conanfile in /home/conan/w/prod-v2_cci_PR-18587/recipes/librasterlite2/all/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-18587/recipes/librasterlite2/all/conanfile.py", line 4, in <module>
      from conans import AutoToolsBuildEnvironment, tools
  ImportError: cannot import name 'AutoToolsBuildEnvironment' 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.}