[question] conan2 export-pkg fails for conanfile.py with python_requires dependency not in the local cache
### What is your question?

Hi,

We started an experimental migration of our packages to conan 2.x.
Our packages use python_requires to declare a base dependency for our conanfiles which works fine with conan 1.x but has changed behaviour with conan 2.x

In our consumer conanfiles we use the following:
```
class MyPackageConan(ConanFile):
    name = "mypackage"
    version = "0.0.1"
    python_requires = "conan_file_base/2023.01"
    python_requires_extend = "conan_file_base.MyConanFileBase"
    ...
```
We then package the packages with conan export-pkg:

`conan export-pkg -r myremote mypackage/conanfile.py`

In case conan_file_base is not yet in the local cache, but available on the remote repository myremote export-pkg with conan 2.x seems to fail even though the remote is defined on the command line with -r myremote:
```
...
conan_file_base/2023.01: Not found in local cache, looking in remotes...                                                                                                                                                           
ERROR: Error loading conanfile at '.../mypackage/conanfile.py': Cannot resolve python_requires 'conan_file_base/2023.01': No remote defined
...
```

Explicitly downloading the python_requires dependency before export-pkg solves the issue:
`conan download conan_file_base/2023.01 -r myremote`

**Question**
- Is this an intended behavior change to enforce conan downloads for python_requires compared to conan 1.x?
The errror message "No remote defined" even though a remote is defined on the command line seems to suggest that this is a bug.

```
conan --version
Conan version 2.0.2
```

### Have you read the CONTRIBUTING guide?

- [X] I've read the CONTRIBUTING guide
diff --git a/conan/cli/commands/export_pkg.py b/conan/cli/commands/export_pkg.py
index 1181efa2b..eaeae07da 100644
--- a/conan/cli/commands/export_pkg.py
+++ b/conan/cli/commands/export_pkg.py
@@ -49,7 +49,8 @@ def export_pkg(conan_api, parser, *args):
     remotes = conan_api.remotes.list(args.remote) if not args.no_remote else []
 
     ref, conanfile = conan_api.export.export(path=path, name=args.name, version=args.version,
-                                             user=args.user, channel=args.channel, lockfile=lockfile)
+                                             user=args.user, channel=args.channel, lockfile=lockfile,
+                                             remotes=remotes)
     # The package_type is not fully processed at export
     assert conanfile.package_type != "python-require", "A python-require cannot be export-pkg"
     lockfile = conan_api.lockfile.update_lockfile_export(lockfile, conanfile, ref,
diff --git a/conans/test/integration/command/export_pkg_test.py b/conans/test/integration/command/export_pkg_test.py
index d63b2fdb0..98ae0fd17 100644
--- a/conans/test/integration/command/export_pkg_test.py
+++ b/conans/test/integration/command/export_pkg_test.py
@@ -594,3 +594,17 @@ def test_export_pkg_test_package_build_require():
     assert "RUN TEST PACKAGE!!!!" in c.out
     lock = json.loads(c.load("conan.lock"))
     assert "pkg/1.0" in lock["build_requires"][0]
+
+
+def test_export_pkg_remote_python_requires():
+    """ Test that remote python-requires can be resolved
+    """
+    c = TestClient(default_server_user=True)
+    c.save({"tool/conanfile.py": GenConanfile("tool", "1.0"),
+            "pkg/conanfile.py": GenConanfile("pkg", "1.0").with_python_requires("tool/1.0")})
+
+    c.run("create tool")
+    c.run("upload tool* -r=default -c")
+    c.run("remove * -c")
+    c.run("export-pkg pkg")
+    assert "conanfile.py (pkg/1.0): Exported package binary" in c.out
['conan/cli/commands/export_pkg.py', 'conans/test/integration/command/export_pkg_test.py']