filter api: always treat FILTER_PROPERTY_MATCH_TYPE as an int value

Based on @dregad's comments, this follows up on @dhx's fix.

Fixes #15373: XSS vulnerability
Revert "filter api: always treat FILTER_PROPERTY_MATCH_TYPE as an int value"

This reverts commit 45f9e746fb9a42e74b668211372d9e45db3e7b6c.

This fix reopens the reported vulnerability therefore it is reverted.
Update match_type parameter to be XSS-safe by itself

Use of gpc_get_int() instead of gpc_get_string() prevents malicious
users from passing arbitrary strings as parameter.

Fixes #15388
Display of match_type filter property for unknown types

Prior to this, if for any reason the filter's match type property was
not one of the predefined types (i.e. 'any' or 'all'), the code would
default to 'all', but display a blank string on the filter page. This is
confusing to users, so the display now matches the filter's actual
behavior.

Fixes #15389