fix(amazonq): Fix for incorrect TriggerToResponseLatencyMilliseconds values in JetBrains telemetry

[laileni-aws]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Problem

JetBrains telemetry was reporting astronomically large TriggerToResponseLatencyMilliseconds values (e.g., 2.5271421583E10 ms ≈ 292,493 days) instead of expected values around ~2000ms.

Solution

Added guard clauses to getCodeWhispererEndToEndLatency() and getPerceivedLatency() methods to return 0.0 when timestamps are uninitialized, preventing incorrect latency calculations.

Testing

./gradlew :plugin-amazonq:codewhisperer:jetbrains-community:compileKotlin

Checklist

• My code follows the code style of this project
• I have added tests to cover my changes
• A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
• I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.