fix: correct calculation of execution paths total

[k1LoW]

This pull request updates the calculation of total execution paths in the Metrics function to more accurately account for the number of steps and test cases. Instead of raising the number of steps to the power of test count, it now multiplies the number of steps by 2 raised to the power of test count.

Calculation logic improvement:

• Updated the calculation of executionPathsTotal in the Metrics function in tailor/metrics.go to use len(r.Steps) * int(math.Pow(2, float64(testsCount))) instead of int(math.Pow(float64(len(r.Steps)), float64(testsCount))), providing a more accurate representation of execution paths.

[github-actions]

Code Metrics Report

Coverage	Code to Test Ratio
34.7%	1:1.8

Code coverage of files in pull request scope (100.0%)

Files	Coverage
tailor/metrics.go	100.0%

---

Reported by octocov