CondaPkg.toml not automatically created

**Affects:** PythonCall

**Describe the bug**
When I use PythonCall (through "using PythonCall"), no CondaPkg.toml is created in my current Julia environment, but a central CondaPkg.toml in my user/.julia folder is created/used. I was expecting that per default, every Julia environment automatically gets its own Conda environment.

To reproduce, on a blank environment with an existint project.toml and manifest.toml, add PythonCall and excecute "using PythonCall"

Not perfectly sure if this is a bug or if there is a not-so-obvious way to automatically instantiate CondaPkg.toml per environment.
Thanks for any help.

**Your system**
Please provide detailed information about your system:
Windows 11
Julia 1.10, PythonCall 0.9.15

Base.versioninfo()
```
Julia Version 1.10.0
Commit 3120989f39 (2023-12-25 18:01 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 12 × 13th Gen Intel(R) Core(TM) i7-1355U
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-15.0.7 (ORCJIT, goldmont)
Threads: 1 on 12 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS =
```
Pkg.status()
```
[992eb4ea] CondaPkg v0.2.22
[717857b8] DSP v0.7.9
[7a1cc6ca] FFTW v1.8.0
[b18b359b] FourierTools v0.4.2
[c27321d9] Glob v1.3.1
[a98d9a8b] Interpolations v0.15.1
[6099a3de] PythonCall v0.9.15
[f2b01f46] Roots v2.1.0
[a5390f91] ZipFile v0.10.1

```
CondaPkg.status()
```
CondaPkg Status C:\Users\j.fischer\OneDrive - xxxxxxx\Dokumente\Julia\xxxx\CondaPkg.toml (empty)
Not Resolved (resolve first for more information)
```

Reproduce the report in a blank Julia environment with project.toml and manifest.toml by adding PythonCall and running "using PythonCall". Inspect how CondaPkg.toml is selected or created, then verify whether the environment-local file is created and used instead of the central user/.julia file.

Escrito por el modelo de indexación a partir del texto del issue.