Introducing trt_compile() and example how to use it

[borisfom]

Summary

Introducing lazy TRT compilation support.
Also, a POC of how to add lazy TRT compilation support to MolMIM.
trt_compiler.py as per my plan, will evenually be part of NeMo. (import_utils.py won't be needed for Nemo main as it has safe_import).
Those changes should work across many NeMo versions - I actually had to patch nemo 1.23 to fix export_utils.py bug that was specific to that versions. Most other NeMo versions should work out of the box.

Details

Describe your changes. You can be more detailed and descriptive here.

Usage

How does a user interact with the changed code?

python -m your.new.module -and -all -options

Testing

How do you prove that your code behaves the way you claim?

Tests for these changes can be run via:

pytest -v tests/your/new/or/existing/test_functions.py::test_function

(NOTE: also delete this checklist as you fill-out this PR template)

Most of the changes to files with extensions *.py, *.yaml, *.yml, Dockerfile* or requirements.txt DO REQUIRE both pytest- and jet- CI stages.

• Did you review the Before your PR is "Ready for review" section before asking for review?
• Did you make sure your changes have tests? Did you test your changes locally?
• Can you add the SKIP_CI label to your PR?
• Can you add the PYTEST_NOT_REQUIRED label to your PR?
• Can you add the JET_NOT_REQUIRED label to your PR?