🐛 Bug: noInferableTypes removes incorrectly type from Map variable

[rubiesonthesky]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Expected

This code stays as it is

type MapStringToNumber = Map<string, number>;
const incompleteTypes: MapStringToNumber = new Map();

Actual

It changes to

type MapStringToNumber = Map<string, number>;
const incompleteTypes = new Map();

Additional Info

This was uncovered with changes in #1511

typestat.json

{
	"fixes": {
		"noInferableTypes": true
	},
	"types": {
		"strictNullChecks": true
	}
}

tsconfig

{
	"files": ["actual.ts"]
}

[rubiesonthesky]

In declaredTypeIsEquivalent when comparing Map to Map, they are assignable to each other, so we need to add extra check declaredType.getSymbol()?.getEscapedName() !== "Map" to the first if.

However, then we go to typeSymbolsAndArgumentsAreEquivalent where we are now comparing string and any and again they are assignable to each other.

So we need to have some better check somewhere to say that Map and Map<string, number> are not same thing and we should not remove Map<string, number> from assigned types.