…ening and closing curly brackets.

I am making this change because the current regular expression may confuse a jsDocParam with a jsDocType. Whilst looking into the history of regular expressions, I came to the conclusion that this was simply a relaxation of the rules governing regular expressions to allow for use cases that do not exist.

…t contains a typo:

@template {myType} T
or
@template T

Previously, only the second option worked; in the case of @template {myType} T, “{myType}” was coloured as a jsDocParam and “T” remained as a comment

… tag in jsdocs

It's a lesser-known tag with syntax very similar to `import {Types} from "./path"` in the js module.
We simply reuse the nextgroup from a “@import” syntax match

This way, we also support a syntax like @import * as Types from “./path”

Add support for multiline JSDoc imports using the `@import` syntax.

Example:

/**
 * @import {
 *   Type1,
 *   Type2,
 *   Type3
 * } from "my/module.js"
 */

Introduce a `jsDocStar` syntax type to represent the `*` prefix at the
beginning of JSDoc lines. Reuse it in the `jsModule` group to keep syntax
definitions consistent and improve highlighting.

Tested with multiple JSDoc cases.

Known edge case: invalid patterns like `import\n *\n *` may highlight the
second `*` as a comment. This is not valid/common JavaScript syntax and does
not affect normal usage.

example:

/**
 * @typedef {{
 *	my: string;
 *	superType: boolean;
 * }}
 */
To do this, create a jsDocStar group that uses the comment color for the * characters and preserves the region's color.

I also fixed an issue with jsDocTypeNoParam that didn't support nesting with `extend`.

…-jsDocsType_multiline--jsDocsImportTagSupport

…sDocsType_multiline--jsDocsImportTagSupport