To Kill A Translationbird

If for some reason, you are overriding an existing schema with something particular for your project, you may have run into an edge case. If you need to override a translation, you're fine, but if a translation exists and you just need to remove it? You're out of luck... until now!

Now, you can do this:

```erlang
{translation, 
 "some.key",
 fun(Conf) ->
   %% Do something to something and return translated value
}.

%% Oh no, that won't do at all
{translation, "some.key"}.
```

The second translation removes the first from the list and replaces it with an undefined function. It's important to note that if a third translation was added afterwards, it would override that deletion.