Always preserve comments with --minify=0 is used

[sbc100]

This is useful for folks who want to run the closure compiler as an external step, after linking.

Fixes google-internal issue: https://buganizer.corp.google.com/issues/287520718

[kripken]

Makes sense to me, because --minify=0 is only used for debugging and not production builds. For a debug builds, adding comments is no burden and can only help.

Maybe worth mentioning that in the changelog and the setting's docs?

[sbc100]

I did update the changelog.

[kripken]

Suggested change

	compiler or some other tool that gives comments semantic meaning.
	compiler or some other tool that gives comments semantic meaning (and
	should have no downside, as `--minify=0` is only used in debug builds anyhow).

[sbc100]

I'm not sure about that though... --minify=0 isn't just for debug builds.. it might be useful in release builds too, if folks want to do their own minification later on the pipeline.

[kripken]

Yeah, maybe you're right. I just think it would be good to explain why we don't think this will inconvenience existing users. So it's either a debug build, or one that the user will minify later anyhow, and either way we aren't hurting anything.

[sbc100]

Yeah .. I guess we could say something like.. "which is in keeping the with spirit of minify=0 which is designed for folks who either want to debug their code to perform their own minification". I'm not sure its worth the extra sentence though.

[kripken]

Sounds good.

I added a comment with an idea for a further explanation in the changelog.