Port #32947 to release-3.6

[weswigham]

Resolve SymbolFlags.Type only at first in jsdoc getTypeFromTypeReference before falling back to SymbolFlags.Value.

Previously, by having both simultaneously at first, we'd find the local symbol of a merged const/type alias symbol, which only actually has value meaning applied to it. In normal codepaths, we'd skip over that to the export symbol of the same name, which has the intended type meaning.

This fixes a regression in the webpack user test. (When we started binding @enum tags a typedefs, we started having merged const/type aliases with separate export/local symbols in js (just like in TS), which were previously much harder to make)

[weswigham]

@DanielRosenwasser pls we never merged this into 3.6 - if we are cutting a 3.6.4 at some point, this should probably be in it - this was a fix for a break in a thing webpack's js did.

[weswigham]

Or if conversely you're not interested in this, closing the PR would be nice ❤️