ci: Enable TF-TRT tests

[pskiran1]

What does the PR do?

This PR re-enables the L0_tftrt_optimization and L0_warmup TF-TRT tests that have been disabled since 24.05.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

Where should the reviewer start?

Test plan:

• CI Pipeline ID: 16218566

Caveats:

Background

In the 24.05 release, implicit batch support was removed as part of the TRT v10 upgrade. As a result, the TF backend was unable to build TF-TRT engines for implicit batch TF models because it was using implicit batching by default. In the upcoming TF release, the TF backend will use dynamic batching by default, enabling it to successfully build TF-TRT models.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

[tanmayv25]

Don't merge just yet. Once the r24.07 branch is ready, then merge these changes into that branch.

[krishung5]

@pskiran1 Could you change the target branch to r24.07?
NVM, I saw that the release branch is up to date with main, so went ahead and changed it.

The base branch was changed.

[mc-nv]

can we change target branch to main I don't see any value in this change for release branch.

[krishung5]

@mc-nv I have no strong objections to change it to target main since it's only change in comments in the tests, but I would still slightly prefer to merge it into the release branch first, then merge into main after 24.07 gets released. The reason being that, the implicit batch will only be supported from 24.07 upstream while as of now the main hasn't been advanced to 24.07 DLFW yet and hence doesn't have the support for implicit batch.