challenge(formatter): noInitializerWithDefinite rule

[Yash-Singh1]

Summary

This PR removes the bogus marking of TypeScript variable definitions with definite assertions that are initialized and instead moves it to a new lint rule noInitializerWithDefinite.

[yashsingh1]: Hi there, I was working on the typescript/definite/definite test case and traced the problem to definite declarations being marked as bogus by the parser here: https://github.com/biomejs/biome/blob/main/crates/biome_js_parser/src/syntax/stmt.rs#L1393. Would it be reasonable to not enter bogus mode as this can be considered as a compiler error instead of a syntax error?

[ematipico]: I think it's possible to change that, and create a syntax rule inside our analyzer

We already do that for a couple of cases https://github.com/biomejs/biome/blob/main/crates/biome_js_analyze/src/syntax/correctness/no_super_without_extends.rs

(https://discord.com/channels/1132231889290285117/1132602615570649110/1175767286968242266)

Test Plan

I added some test cases on biome_js_analyze and also have 100% Prettier Similarity for typescript/definite/definite.

[TaKO8Ki]

I guess you may need to run just ready or just codegen.

[ematipico]

That's great!

[Conaclos]

Thanks for your contribution! I left one comment.