@typedef's nested Object syntax disallows type arguments

[sandersn]

Previously the jsdoc index signature syntax was incorrectly treated the same as Object:

/** @typedef {Object} AllowsNesting
 * @property ... */
/** @typedef {Object.<string,string>} IncorrectlyAllowsNesting */

Fixes #34911

The creator of the issue expected @property to work with Object.<string,string> as well, but that's not documented on jsdoc.app.
For example, @typedef could allow combining @typedef {Object<string,string>} X with @property {string} p to create type X = { [s: string]: string, p: string }.

[sandersn]

@weswigham you might be interested too, since you've worked with @typedef quite a bit before.

[elibarzilay]

One side-comment: shouldn't there be some warning or some indication that stuff that you thing is doing something is actually ignored?

[sandersn]

@elibarzilay We assume that lots of jsdoc with checkJS is still incorrect and it would be annoying to have errors on it all. We've thought about a strictCheckJS mode before but haven't come to any conclusions. Might be time to revisit the question.