Instrumentation: fix log trace inconsistent status code with error result chaining

[1pkg]

Motivation/summary

This fix is branched from #15117.

This PR introduces additional error request.Result chaining for secondary errors that can happen after the response has already been written e.g. timeout or panic. The rationale behind this change to create an ability to pass multiple errors in the result object so they could be eventually logged while maintaining original response.

As a result of this changes self instrumentation transaction will always contain original error, while logging middleware will log both the original error and the secondary timeout error.

This is alternative to errors chaining PR #15123 which will use single error depending on when timeout happened.

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

#15123
#15117
#14232

[mergify]

This pull request does not have a backport label. Could you fix it @1pkg? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

[carsonip]

I agree that this looks like an overkill which further complicates a part that is already failing due to its complexity. Let's work on #15123

[1pkg]

I agree that this looks like an overkill which further complicates a part that is already failing due to its complexity. Let's work on #15123

I agree, that this approach introduces too much complexity for a little benefit.

[1pkg]

Closing this in favor of simple timeout check version from #15123