Improve CLI speed with lazy imports

Description

This is an optional PR to consider. Because of too many imports getting executed in various __init__.py files throughout the library, the CLI is slow to start up. The initialization of so many imports also makes the initial import of graphrag slow as well.

Proposed Changes

Following some tips from this article, I profiled the startup time for the entire library with a focus on improving the CLI startup time using the following commands:

python -X importtime -c 'from graphrag.cli.main import *' 2> graphrag-imports.log
tuna graphrag-imports.log

import statements involving very large libraries or long-processing times were moved inside the function calls that rely on them.
nearly all __init__.py files across the entire package are empty now.
relative imports were converted to absolute imports to avoid the circular import problem
comments were added in places where import statements may appear unusual at first explaining why they were moved there

The following screenshot shows the startup time for the CLI code when the package is first installed. graphrag-initial-startup-time

After the library has been loaded once (python generates bytecode to speed up future imports), we can achieve an even faster load time of 0.3 seconds.

graphrag-cached-startup-time

Tab completion with the CLI is also now very responsive.

Checklist

[x] I have tested these changes locally.
[x] I have reviewed the code changes.
[x] I have updated the documentation (if necessary).
[x] I have added appropriate unit tests (if applicable).

Additional Notes

This PR closes https://github.com/microsoft/graphrag/pull/1299 as well.

A small patch for Typer path completion was added to the CLI to improve the CLI experience.

microsoft / graphrag