Fix noopAsync to return Promise<void> instead of Promise<number>

[Copilot]

The noopAsync function was incorrectly returning Promise<number> by using Promise.resolve(0), but as a no-op function it should return Promise<void> since it doesn't produce any meaningful value.

Changes Made

• Updated utils/noop.ts to change Promise.resolve(0) to Promise.resolve()
• Added explicit Promise<void> return type annotation for clarity
• The function now correctly returns Promise<void> as expected for an async no-op function

Before

export function noopAsync() {
    return Promise.resolve(0);
}

After

export function noopAsync(): Promise<void> {
    return Promise.resolve();
}

This change ensures type consistency and follows the expected behavior where no-op functions should not return meaningful values.

Fixes #43.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.