feat: Implement Dynamic shapes + fallback support for export path

[peri044]

Description

Implement Dynamic shapes + fallback support for export path

TLDR:

1. We need torch inputs at a few places in the codebase and to perform shape analysis. We also need torch_tensorrt.Input objects to hold the dynamic shape information accordingly for graph/subgraph inputs. Input.torch_tensor attribute is created to handle this and utility functions get_torch_inputs can be used. prepare_inputs can only return torchtrt_inputs now. Ideally, I think it would be convenient if Input objects are used through out the code and get_torch_inputs can be used whenever necessary.
2. I added support for kDouble enums. We support truncation and accept graphs which have torch.float64 as inputs and casts are added internally. But our Input object errors out if the dtype is torch.float64.
3. Updated aten_tracer to use constraints to set bounds on Input dimensions. These bounds are dictated by TensorRT. The dynamic dimensions cannot be unbounded.

Fixes # (issue)

Type of change

Please delete options that are not relevant and/or add your own.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project (You can use the linters)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas and hacks
• I have made corresponding changes to the documentation
• I have added tests to verify my fix or my feature
• New and existing unit tests pass locally with my changes
• I have added the relevant labels to my PR in so that relevant reviewers are notified

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to C++ style guidelines

[github-actions]

Code conforms to Python style guidelines

[gs-olive]

Added a small comment on documentation. Otherwise looks good to me!

[gs-olive]

Add a reference to this document in index.rst to have it reflect on the webpage

[peri044]

done. thanks

[github-actions]

Code conforms to Python style guidelines

[github-actions]

Code conforms to C++ style guidelines