new filter 'translate'

uses a `.yaml` file as a dictionary to translate words or phrases in a field.

default dictionary of `http response codes` included in the filter for ease of testing.

example dictionary file used to test yaml formatting -  `dictionary.yaml` containing 

```
"301": that shit is bananas
"GET": POOP
"wordpress": more like stupid press
```

tested both `exact` true/false matching ...   and made sure I could translate into the same field by setting the `field` and `destination` config parameters to be `@message`  which made for a rather opinionated apache log.

![translate_filter_output](https://f.cloud.github.com/assets/2488346/102038/20f1f1d6-690a-11e2-9112-009cb4a62e1f.png)

I guess the obvious next step would be to make a `l33t` or `Pirate` dictionary to be the default rather than response codes.