fix(parser): forbid abstract class members with implementation in parser instead of semantic

[ulrichstark]

The following four cases are now errors in parser instead of semantic errors.
TS Playground for reference.
Closes #14013

abstract class Foo {
  abstract prop = 3;

  abstract method() { }

  abstract get getter() {
    return 1;
  }

  abstract set setter(value: number) {
    
  }
}

[Copilot]

Pull Request Overview

This PR moves validation of abstract class members with implementation from semantic analysis to parser level, providing earlier error detection. The change ensures that abstract properties with initializers, abstract methods with implementations, and abstract accessors with implementations are caught during parsing rather than later semantic validation.

• Moves abstract member validation logic from semantic checker to parser
• Removes semantic validation functions and imports for abstract member checking
• Adds new parser diagnostic functions for abstract member validation errors

Reviewed Changes

Copilot reviewed 4 out of 8 changed files in this pull request and generated no comments.

File	Description
crates/oxc_semantic/src/checker/typescript.rs	Removes abstract member validation functions and import cleanup
crates/oxc_semantic/src/checker/mod.rs	Removes property definition check call
crates/oxc_parser/src/js/class.rs	Adds abstract member validation logic in property and method parsing
crates/oxc_parser/src/diagnostics.rs	Adds new diagnostic functions for abstract member errors

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #14325 will not alter performance

_{Comparing ulrichstark:forbid-abstract-class-members-with-implementation-in-parser-instead-of-semantic (e659c9e) with main (0c14e50)}

Summary

✅ 37 untouched

[fisker]

Can't approve since I don't have access, but LGTM.