Fix: Exclude generator functions from convert-to-class suggestions

[Copilot]

Generator functions (function*) were incorrectly triggering the TS80002 diagnostic "This constructor function may be converted to a class declaration". This is incorrect because generator functions have special semantics that are incompatible with class constructors.

Problem:

function* gen() {}
gen.prototype.next = gen.prototype.next;
gen.prototype.return = gen.prototype.return;

The above code would incorrectly trigger the convert-to-class suggestion, even though generator functions cannot be meaningfully converted to classes.

Solution:
Added checks in the canBeConvertedToClass function to exclude generator functions by testing for FunctionFlags.Generator in both function declaration and function expression paths.

Changes:

• Modified src/services/suggestionDiagnostics.ts to exclude generator functions
• Added comprehensive test coverage for generator declarations, generator expressions, and mixed scenarios
• Verified that regular constructor functions continue to work correctly

Testing:

• All existing tests pass
• New tests verify generator functions don't trigger the diagnostic
• Regular constructor functions still correctly trigger the diagnostic when appropriate

Fixes #62056.

---

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

[RyanCavanaugh]

Run npx hereby format and commit that

[Copilot]

Run npx hereby format and commit that

Ran npx hereby format - no formatting changes were needed as the code is already properly formatted.