Avoid creating extra lrp mappings in logsearch
Avoid creating extra lrp mappings in logsearch

We have an issue with a log message from the auctioneer. It contains:
`"data":{"lrps":{"df03138b-924d-417e-9743-abf81e577a70-7276869e-d03c-4ffd-9f83-18c366a390c3":[1]},...,"request":"/v1/lrps",...}`
Elasticsearch assumes
`auctioneer.data.lrps.df03138b-924d-417e-9743-abf81e577a70-7276869e-d03c-4ffd-9f83-18c366a390c3`
is the name of a field, because it contains an array of integers. So it
creates a mapping for each new LRP GUID.

This commit adds a logstash filter that changes the hash to an array
containing the GUID strings.

This depends on the code from PR
https://github.com/cloudfoundry-community/logsearch-for-cloudfoundry/pull/211

alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf