Inconsistency in usage of CITimeVerbose to generate compilation logs

For C2 logging of timing information for each phase to tty and to compilation log is controlled by CITimeVerbose [0]. However, for C1 CITimeVerbose only controls the logging of timing information to tty and not to the compilation log [1].
Logging to tty for both C1 and C2 is done in TraceTime [3] - that explains the common behavior for tty.

This difference in logging behavior can be a source of confusion when timing information for C1 and C2 compilation phases is required, which can be easily avoided if C1 follows the same behavior as C2.

[0] https://github.com/openjdk/jdk/blob/489a32fe40e2a2c539296d51d4ffc0abc036d33c/src/hotspot/share/opto/compile.cpp#L4336-L4338
[1] https://github.com/openjdk/jdk/blob/489a32fe40e2a2c539296d51d4ffc0abc036d33c/src/hotspot/share/c1/c1_Compilation.cpp#L88-L90
[2] https://github.com/openjdk/jdk/blob/489a32fe40e2a2c539296d51d4ffc0abc036d33c/src/hotspot/share/runtime/timerTrace.cpp#L78-L86