Core: The `index.query.parse.strict` setting also fails if queries refer to unmapped fields.

Also the percolator and filter parsing for aliases enforce strict query parsing

Strict parsing for percolator and filter alias parsing is only enforced on indices created after to upgrade to `1.4.0`

PR for #6664
I don't think it is ok to use the same configuration parameter for
 - throwing an error on unmapped fields
 - throwing an error on deprecated options.