Edit: It turns out that the semantics below only work for overloads that specify a return type. Otherwise the parser doesn't know where the last @overload ends if it's missing @return. While noImplicitAny prompts to add @return, it's off in most JS scenarios.

I'm still not happy that we're encouraging people to split their tags, but I don't see a good way around it.

Nope, Below Idea Doesn't Work

Also, make @overload work like other jsdoc tags: only the last jsdoc tag
before a declaration is used. That means all overload tags need to be in
one tag:

/**
 * @overload
 * @return {number}
 *
 * @overload
 * @return {string}
 */

function f() { return "1" }

This no longer works:

/**
 * @overload
 * @return {number}
 */
/**
 * @overload
 * @return {string}
 */
function f() { return "2" }

@DanielRosenwasser this is a break from what is described in the beta blog post, but I really want @overload to work the same way as the rest of our jsdoc tags. At the time I changed the existing tag's behaviour, I found that almost nobody split their tags out this way, so I don't want to encourage people to start.

Fixes #52367
Followup to #51234