✨[Feature] Add the ability to set breakpoints in the compilation process.

[narendasan]

Is your feature request related to a problem? Please describe.

Sometimes you want to pause or break compilation of a graph at a certain point to see what is happening at that operation. This can help figure out what is happening in the conversion process without having to recompile the entire library.

Describe the solution you'd like

At least for the conversion process it should be possible to specify a debugName of a Value and stop conversion and dump the state of the conversion context. This would include all arguments, the target function signature, and the node info.

Describe alternatives you've considered

People would need to add debug statements to the library themselves

Additional context

Related to #1235, #949

[narendasan]

Similarly this could be helpful in partitioning @bowang007. Though we need to centralize the context first to do this I would think.

[narendasan]

See #1263 for a first draft of this.

[narendasan]

I am thinking the way this would work is you would do something like:

torch_tensorrt.compile(module,
    inputs=...,
    breakpoints=["%32","@12"],
    dump_context=["%input.2", "@3"]
)

where breakpoints would interrupt conversion / partitioning and pause / maybe cancel conversion after that point. And context dumps would dump context at those ops onto the debug log.

[narendasan]

This should be phase 1. The next phase should include pulling out value debug names based on python level symbols provided by the user

[narendasan]

Probably a M sized task