fix(core): repair malformed runStep, restore tests and config

[arpit2006]

Pull Request Overview

This Pull Request resolves a TypeScript compilation failure caused by a malformed and duplicated implementation of the runStep method in runtime.ts.

The existing code contained overlapping logic between runStep and runStepWithRetry, resulting in invalid method signatures, mismatched function bodies, and parser errors that prevented successful project builds. This change restores proper method separation, removes duplicate declarations, and ensures both methods have valid TypeScript syntax and well-defined responsibilities.

By correcting the method structure, the runtime execution flow is preserved while restoring build stability and developer productivity.

---

Related Issues

• Resolves #<issue_number>

---

Architecture and Implementation Details

• Refactored the runStep implementation to ensure a single valid method declaration.
• Removed duplicated and partially merged code blocks that overlapped with runStepWithRetry.
• Separated execution logic between runStep and runStepWithRetry according to their intended responsibilities.
• Corrected method signatures, parameter definitions, return types, and brace structure.
• Eliminated TypeScript parser errors caused by malformed syntax.
• Verified compatibility with the existing runtime execution workflow.
• Ensured the project compiles successfully without introducing behavioral changes.

---

Breaking Changes

• Yes (Describe below)
• No

This change only fixes an invalid implementation and does not modify public APIs, configuration schemas, or runtime behavior.

---

Testing Methodology

1. Executed TypeScript build validation to confirm successful compilation.
2. Verified that runtime.ts no longer produces syntax or parser errors.
3. Confirmed that both runStep and runStepWithRetry are independently recognized by the TypeScript compiler.
4. Performed local validation of runtime execution flow to ensure no regressions were introduced.
5. Ran linting checks to verify formatting and code quality standards.

---

Performance & Observability Impact

• No measurable performance impact.
• No additional memory overhead introduced.
• No telemetry, logging, tracing, or observability changes were made.
• This update is strictly a compilation and code-structure fix.

---

Contributor Checklist

• I have read and adhered to the PulseStack Contributing Guidelines.
• I have successfully executed the local test suite without errors.
• I have updated the corresponding documentation to reflect these changes.
• I have added adequate test coverage for my implementation.
• I have verified that my code aligns with the repository's formatting and linting standards.

[arpit2006]

@NEXARA-oss , Requesting Review!