Applications that explicitly configure lager's `crash_log` with the
value `undefined` will get a really terrible crash message for all
versions since 81222ca486
Diff here: 81222ca486 (diff-25e915f0df09d04052d2a6e85b8824f2)
That message looks like this:
```
** Generic server lager_crash_log terminating
** Last message in was rotate
** When Server state == {state,undefined,
{file_descriptor,prim_file,{#Port<0.1340>,15}},
281571,65536,10485760,
[{hour,0}],
5,false}
** Reason for termination ==
** {badarg,[{erlang,'++',[undefined,".3"],[]},
{lager_util,rotate_logfile,2,
[{file,"_build/default/lib/lager/src/lager_util.erl"},
{line,220}]},
{lager_crash_log,handle_info,2,
[{file,"_build/default/lib/lager/src/lager_crash_log.erl"},
{line,99}]},
{gen_server,try_dispatch,4,[{file,"gen_server.erl"},{line,601}]},
{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,667}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
```
This fix will allow people who use this legacy configuration to not
experience production crashes at midnight after the deploy, when
crash_log tries to rotate for the very first time, resulting in trying
to append `.Int` to `undefined`