Adjust the property endpoint to the OpenRefine 3.5 behavior

OpenRefine 3.5 sets type parameter of the data extension property proposal requests to the service's schemaSpace value which obviously doesn't match any existing type. Current implementation just skips the type-based property filtering if the type parameter doesn't match any known type.