Fixed a crash related to computed enum member keys

[Andarist]

Enum members are in the scope of the enum declaration as this is allowed:

declare const enum E {
  foo = "foo",
  foobar = foo + "bar",
}

That allows the identifier in the computed key to attempt resolving in the same way. However, that leads to a cycle with enums:
getDeclaredTypeOfEnum(E) -> hasBindableName -> isLateBindableName -> checkComputedPropertyName -> checkExpression -> checkIdentifier -> getNarrowedTypeOfSymbol -> getTypeOfSymbol -> getTypeOfEnumMember(E.foo) -> getTypeOfEnumMember -> getDeclaredTypeOfEnumMember -> getDeclaredTypeOfEnum(E)

Given enums can't really have computed keys (as shown in the added tests given the reported "TS1164: Computed property names are not allowed in enums." diagnostic), the simplest fix is to just check if the member !hasDynamicName(member) instead of hasBindableName(member) (the latter calls || isLateBindableName(member))

fixes #63173

[jakebailey]

Can you explain the fix?

[Andarist]

@jakebailey sure, edited the PR summary