Improve error messages when indexing into a type

[dragomirtitian]

Fixes #30241

This PR introduces more explicit error messages when trying to index into a type without an index signature.
Rules:

• When the index argument is a string literal, number literal or unique symbol, but the target object does not have the corresponding property the error will be:

Element implicitly has an 'any' type because expression of type 'LITERAL_TYPE' can't be used to index type 'TARGET_TYPE'.
  Property 'PROP_NAME' does not exist on type 'TARGET_TYPE'

• When the index argument is a union of literals, the error message will contain the union used to index, and will contain the first property in the union that is not found in the type:

Element implicitly has an 'any' type because expression of type 'UNION_OF_LITERAL_TYPES' can't be used to index type 'TARGET_TYPE'.
  Property 'FIRST_MISSING_PROP_NAME' does not exist on type 'TARGET_TYPE'

• When the index argument is string or number the error will warn about the missing index on the target type:

Element implicitly has an 'any' type because expression of type 'STRING_OR_NUMBER' can't be used to index type 'TARGET_TYPE'.
  No index with a parameter of type 'STRING_OR_NUMBER' was found on type 'TARGET_TYPE'

Examples:

const o = { a: 0 };

declare const k:"b";
o[k]; // rule 1
// Element implicitly has an 'any' type because expression of type '"b"' can't be used to index type '{ a: number; }'.
//   Property 'b' does not exist on type '{ a: number; }'

declare const k2: "b" | "c";
o[k2]; // rule 2
// Element implicitly has an 'any' type because expression of type '"b" | "c"' can't be used to index type '{ a: number; }'.
//   Property 'b' does not exist on type '{ a: number; }'.

declare const nIndex: number;
o[nIndex] // rule 3
// Element implicitly has an 'any' type because expression of type 'number' can't be used to index type '{ a: number; }'.
//   No index with a parameter of type 'number' was found on type '{ a: number; }'