Infer from usages should not widen literal types

Bug Report

🔎 Search Terms

string literal to string, infer type from usages, code fix, quickfix

⏯ Playground Link

Playground link with relevant code

💻 Code

let a

a = "foo" as "foo" | "bar"

let b

b = getB()

checkB(b)

function checkB(toCheck: "foo" | "bar") {
}

function getB(): "foo" | "bar" {
    return "foo"
}

🙁 Actual behavior

After running infer from usages quickfix, you get string type in a and b positions

🙂 Expected behavior

Should get inffered type "foo"

I think in case of as and satisfies clauses the type should be just copied literally?

As you can see from example this is common case for string enums, like when some function expects some string enum instead of just string, but this information gets lost

Reproduce the behavior in the linked TypeScript Playground using the supplied code, then trace the “infer from usages” quickfix and its handling of assertions or satisfies clauses. Done means the inferred types for a and b preserve the literal "foo" rather than widening to string, with coverage for the shown case.