refactor(semantic/jsdoc): JSDocTag parser rework

[leaysgur]

Address #2642 (comment)

oxc/crates/oxc_semantic/src/jsdoc/parser/jsdoc_tag.rs

Lines 3 to 25 in 0fd67cb

	// Initially, I attempted to parse into specific structures such as:
	// - `@param {type} name comment`: `JSDocParameterTag { type, name, comment }`
	// - `@returns {type} comment`: `JSDocReturnsTag { type, comment }`
	// - `@whatever comment`: `JSDocUnknownTag { comment }`
	// - etc...
	//
	// However, I discovered that some use cases, like `eslint-plugin-jsdoc`, provide an option to create an alias for the tag kind.
	// .e.g. Preferring `@foo` instead of `@param`
	//
	// This means that:
	// - We cannot parse a tag exactly as it was written
	// - We cannot assume that `@param` will always map to `JSDocParameterTag`
	//
	// Therefore, I decided to provide a generic structure with helper methods to parse the tag according to the needs.
	//
	// I also considered providing an API with methods like `as_param() -> JSDocParameterTag` or `as_return() -> JSDocReturnTag`, etc.
	//
	// However:
	// - There are many kinds of tags, but most of them have a similar structure
	// - JSDoc is not a strict format; it's just a comment
	// - Users can invent their own tags like `@whatever {type}` and may want to parse its type
	//
	// As a result, I ended up providing helper methods that are fit for purpose.

[codspeed-hq]

CodSpeed Performance Report

Merging #2765 will improve performances by 3.01%

_{Comparing jsdoc_tag-rework (0fd67cb) with main (3c9e77d)}

Summary

⚡ 1 improvements
✅ 33 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	jsdoc_tag-rework	Change
⚡	parser_napi[pdf.mjs]	76.5 ms	74.3 ms	+3.01%

[Boshen]

Thank you!