Incorrectly calculates the response time of parent sampler at the end of the test when using Transaction controller along with timers and duration of test

**Deepambika** ([Bug 64396](https://bz.apache.org/bugzilla//show_bug.cgi?id=64396&redirect=false)):
Analyzed the JMeter calculation with when we run with transaction controller with generated parent sample

Tested with and without Timers in script - (to check the mismatch occurs only when we use timers with a duration)

For example: Tried 5 users infinite loop count and 5 min duration with timer - At the end of the execution alone the child and parent sample response time calculation works weird like showing more response time than the addition of child samples, maybe the reason it adding the think time for further non-executed samples

Tried in a different version of JMeter to confirm the above findings - could observe similar behaviors in the latest version as well

Please find the attached script and sample result. Below is the findings from the attached result,

From the very Last entries with null response message for parent of Jtl could see more response time in parent alone below is one example,

Parent response time = 4710 ms
but its child has = 1711 ms

Created attachment [SampleScript_GoodreadsSearch.zip](https://apache.github.io/jmeter-bugzilla-attachments/96/64396/37205/SampleScript_GoodreadsSearch.zip): Contains Sample Script and sample result

Severity: major
OS: All

Duplicates:
* https://github.com/apache/jmeter/issues/5315

Start with the attached SampleScript_GoodreadsSearch.zip and its sample result, reproducing the Transaction Controller scenario with timers, a duration limit, and generated parent samples. Compare the final parent response time with the child sample totals and check duplicate issue #5315 for the current status before making changes.

Written by the indexing model from the issue text.