Description

Replaces the usage of doctrine with comment-parser.

Notable differences:

1. Tuples are no longer surrounded by parens
2. No types are normalized, they're left the way they are in the declaration rather than being parsed and then normalized

Notable issues with comment-parser.

1. The library parses the following:

/**
 * @return {string} The description for a return.
 */

as

{
        "tag": "return",
        "name": "The",
        "type": "string",
        "optional": false,
        "description": "description for a return.",
}

Note that the description of the return is split into two... this appears to be a difference in convention, some folks name their return values. We tend not to do so. Regardless, the library does this for all tags so you'll see something resembling `${tag.name} ${tag.description}` places where previously we could just use the description. I don't personally see this as an issue, it's just a quirk of the library, but I could see this getting in the way of adopting this approach if folks think it's too fragile or something like that.

Notable is that I don't think this is a bug in the library, I think it's just the way it parses based on some conventions. It's a little silly for tags like @see but I think it's livable.

How has this been tested?

Tests pass and documentation generation still works as expected (with some minor changes given the new parser)

Types of changes

Non-breaking changes

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

Fixes #26971