fix(wizard): wizard remains in "not ready" state if a custom init() was provided

[muaydin]

Problem

The wizard remained in a "not ready" state if a custom init() was provided, requiring manual toggles in the test code.

Solution

• Wrap the user’s init() with a small decorator that sets _ready = true.
• Remove the manual toggles in wizardTestUtils.ts, letting the wizard handle readiness on its own.

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[justinmk3]

Remove the manual toggles in wizardTestUtils.ts, letting the wizard handle readiness on its own.

Nice 👍

[justinmk3]

can the eslint ignore be avoided, by something like:

Suggested change

	// eslint-disable-next-line @typescript-eslint/unbound-method
	const _init = this.init
	const _init = this.init.bind(this)

[muaydin]

Thanks for pointing that out! I've replaced .apply(this) with .bind(this), which fixes the unbound method issue and removes the need for the ESLint comment.

[justinmk3]

Thanks! Will wait for reply to my comment