Fix: Add input validation for safe logarithm calculations in AugenPriceSpike

[JosueNina]

Description

Added validation to ensure that previousPoint and previousPoint2 are non-zero before performing the logarithm operation to prevent division by zero and avoid log(0) errors. Additionally, included a unit test to verify the correctness of the validation logic.

Related Issue

Closes #8435

Motivation and Context

This change is necessary to ensure that logarithm calculations are safe, preventing runtime errors from division by zero and undefined log(0) operations. This improves the stability and reliability of the application by ensuring that invalid input values are properly handled.

Requires Documentation Change

No, this change does not require updates to documentation as it only involves input validation and adding a unit test.

How Has This Been Tested?

Tested the validation logic with unit tests, verifying that the inputs to the logarithm calculation are correctly checked for non-zero values. The unit test confirmed that division by zero and log(0) cases are handled properly, preventing runtime errors.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[Martin-Molinero]

Thank you!