Fixing records deserialization issue when JsonIgnore is used with same json property name

[iifawzi]

Hey, following up on #5073, this PR resolves the second issue reported at #4628.
With this change, we will not attempt to rename any properties to be ignored, this way the field will not be removed from the ignorable list here.

jackson-databind/src/main/java/com/fasterxml/jackson/databind/introspect/POJOPropertiesCollector.java

Lines 1436 to 1449 in 25e1135

	if (_replaceCreatorProperty(_creatorProperties, prop)) {
	// [databind#2001]: New name of property was ignored previously? Remove from ignored
	// 01-May-2018, tatu: I have a feeling this will need to be revisited at some point,
	// to avoid removing some types of removals, possibly. But will do for now.
	// 16-May-2020, tatu: ... and so the day came, [databind#2118] failed
	// when explicit rename added to ignorals (for READ_ONLY) was suddenly
	// removed from ignoral list. So, added a guard statement above so that
	// ignoral is ONLY removed if there was matching creator property.
	//
	// Chances are this is not the last tweak we need but... that bridge then etc
	if (_ignoredPropertyNames != null) {
	_ignoredPropertyNames.remove(name);
	}

which can be finally excluded during deserialization.