Include command line, localization info and env vars on AM launch failure

While trying to diagnose AM launch failures, its important to be able to get at the final, expanded CLASSPATH and other env variables. We don't get that today: you can log the unexpanded values on the client, and tweak NM ContainerExecutor log levels to DEBUG & get some of this —‚ut you don't get it in the task logs, and tuning NM log level isn't viable on a large, busy cluster.

Launch failures should include some env specifics:

1. list of env vars (ideally, full getenv values), with some stripping of "sensitive" options (i'm thinking AWS env vars here)
2. command line
3. path localisations

These can go in the task logs, we don't need to include them in the application report.