Deprecate validate_* and normalize_*

[nknize]

No need to carry 3 validate and 3 normalize options in GeoPointFieldMapping. This is just causing confusion. This change deprecates the validate_lat, validate_lon, normalize_lat, and normalize_lon options on the geo_point field mapping and simplifies the options by using just validate and normalize, respectively. Geo filters have been updated to include a validate and normalize option to provide consistency with the field mapping defaults. Unit tests and documentation have also been updated.

closes #10170

[rjernst]

Given how we've done other deprecations and removals, I think we need to maintain backcompat for at least reading and ignoring these settings in 2.0? Also, I think it is better to add move the version check to the else if and invert, then have a comment like // ignore legacy setting inside the block. For newer indexes, the setting would fall through and show up as an unknown setting.

[nknize]

I like that idea. I'm a big fan of avoiding exceptions if at all possible but wasn't sure how we've handled bwc in other cases. That will let us remove the 'breaking' label too? Committing a change shortly for review. Will also need to add more thorough testing before merging. I just needed this valuable feedback.

[rjernst]

@nknize I left a couple comments.

@clintongormley Maybe you have some thoughts on whether the breaking change should happen for 1.6 or 2.0?

[dakrone]

@clintongormley I think deprecate in 1.6.0 and remove in 2.0.0, what do you think?

[clintongormley]

Wondering if we should make the whole change (including removing validate) in 2.0. So just mark the options as deprecated in 1.6, eg:

|`validate` | deprecated[1.6.0, This parameter will be removed in 2.0] Set to `false` to accept geo points with invalid latitude or
longitude (default is `true`). *Note*: Validation only works when
normalization has been disabled. This option will be deprecated and removed

[clintongormley]

@nknize any movement here?

[nknize]

@clintongormley looks like my issue notification was eaten by build failures. I'll deprecate in 1.6.1 and completely remove in 2.0. This one has hung around long enough.

[clintongormley]

@nknize perhaps do something similar to the suggestion here: #11161 (comment)

[martijnvg]

Bumping the version up to 1.7.1 for the today's release.

[nknize]

closing this PR in favor of #12300