Custom_nodes path different from original ComfyUI folder_paths definition.

There is a mismatch of ComfyUI and ComfyUI-Manager folder paths, where you want to run ComfyUI with non-default paths by passing an `extra_model_paths.yaml` file. In this case, ComfyUI-Manager does not save custom modules where it should be. For example, this is a problem if you run ComfyUI in a docker container.

In `comfyanonymous/ComfyUI`, all the folder paths are defined under `folder_paths.py` module. For example, custom_nodes folder path is defined under `folder_names_and_paths["custom_nodes"]` variable.

However, ComfyUI-Manager instead of importing `folder_names_and_paths["custom_nodes"]`, defines its own paths. For example, custom_nodes path is defined as

```
comfy_path = os.path.dirname(folder_paths.__file__)
custom_nodes_path = os.path.join(comfy_path, 'custom_nodes')
```

The solution would be to load all the paths from folder_paths.py module.

Start with ComfyUI's folder_paths.py and compare its folder_names_and_paths["custom_nodes"] definition with ComfyUI-Manager's custom_nodes path handling. Trace the manager operations that save custom modules, then verify with an extra_model_paths.yaml configuration, including a non-default or Docker path. Done means custom modules are saved under the configured custom_nodes directory.

Written by the indexing model from the issue text.