Report parser name and location in XContent deprecation warnings

[romseygeek]

It's simple to deprecate a field used in an ObjectParser just by adding deprecation
markers to the relevant ParseField objects. The warnings themselves don't currently
have any context - they simply say that a deprecated field has been used, but not
where in the input xcontent it appears. This commit adds the parent object parser
name and XContentLocation to these deprecation messages.

[elasticmachine]

Pinging @elastic/es-core-infra (:Core/Infra/Core)

[romseygeek]

ParseField.match() is used in nearly 1,000 places in the code outside of an ObjectParser, so this PR leaves the existing method signature and adds another one, with a BWC layer so that if we don't have the parent parser name then we emit the old version of the error message. We can use the calls to the old signature to find places to convert to using ObjectParser.

I also changed the 'this field has been removed entirely' message to read more easily.

[pugnascotia]

The only suggestion I'd make is about whether it's possible to consolidate the log messages. For example:

Suggested change

	if (parserName != null) {
	deprecationLogger.deprecated("[{}][{}] Deprecated field [{}] used, expected [{}] instead",
	parserName, location.get(), usedName, modernName);
	} else {
	deprecationLogger.deprecated("Deprecated field [{}] used, expected [{}] instead", usedName, modernName);
	}
	String prefix = parserName == null ? "" :
	"[" + parserName + "][" + location.get() + "] ";
	deprecationLogger.deprecated("{}Deprecated field [{}] used, expected [{}] instead", prefix, usedName, modernName);

[pugnascotia]

This doesn't look right 🤔

[romseygeek]

It wasn't!

[pugnascotia]

Sorry, out-of-date diff 😅

[romseygeek]

Thanks for the review @pugnascotia !