conda pkg openssl is restricted to version <3.1 - this prevents installation of recent r-base

Not sure whether this is a bug, probably not?

How can we rely on more recent openssl version, e.g. in order to install a recent `r-base` next to PythonCall?

I got the following error
```
error libmamba Could not solve for environment specs
The following packages are incompatible
├─ openssl >=3,<3.1 is requested and can be installed;
└─ r 4.4 is not installable because it requires
└─ r-base >=4.4,<4.5.0a0 but there are no viable options
├─ r-base [4.4.0|4.4.1] would require
│ └─ libcurl >=8.8.0,<9.0a0 but there are no viable options
│ ├─ libcurl [8.10.0|8.10.1] would require
│ │ └─ openssl >=3.3.2,<4.0a0 , which conflicts with any installable versions previously reported;
│ ├─ libcurl 8.11.1 would require
│ │ └─ openssl >=3.4.0,<4.0a0 , which conflicts with any installable versions previously reported;
│ ├─ libcurl 8.8.0 would require
│ │ └─ openssl >=3.3.0,<4.0a0 , which conflicts with any installable versions previously reported;
│ └─ libcurl [8.8.0|8.9.0|8.9.1] would require
│ └─ openssl >=3.3.1,<4.0a0 , which conflicts with any installable versions previously reported;
├─ r-base 4.4.1 would require
│ └─ libcurl [>=8.9.0,<9.0a0 |>=8.9.1,<9.0a0 ], which cannot be installed (as previously explained);
├─ r-base [4.4.1|4.4.2] would require
│ └─ libcurl >=8.10.1,<9.0a0 , which cannot be installed (as previously explained);
└─ r-base 4.4.2 would require
└─ libcurl >=8.11.1,<9.0a0 , which cannot be installed (as previously explained).
```

The issue names no repository files, tests, or entry points. Start by reproducing the conda solver conflict involving openssl, libcurl, r-base, and PythonCall, then trace where the openssl restriction is declared. Done means determining whether the dependency constraint can be changed and verifying that a recent r-base installs alongside PythonCall.

Written by the indexing model from the issue text.