Mutate Processor mutation_timeouts metrics does not account for early exit

[cmwylie19]

Environment

Device and OS:
App version:
Kubernetes distro being used:
Other:

Steps to reproduce

There are several places in the mutate process where the request will exit early before the final return of the response. This leads to metricCollector incrementing the count for mutation timeouts which is inaccurate. We need to stop the timer to ensure we have accurate metrics.

Expected result

If an early exit occurs, we need to stop the timer.

Actual Result

It is not stopped and the mutation_timeout metric is incremented.

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Additional Context

Add any other context or screenshots about the technical debt here.