Add all compilatino metrics to tlparse output log

[yushangdi]

At src/lib.rs:700, the JSON payload is deserialized into an Envelope, which contains compilation_metrics:
Option<CompilationMetricsMetadata>. When that inner struct is deserialized, serde automatically routes
unknown keys like dynamo_config, is_forward, frame_key, etc. into the extra map.

example output:

At the end of tlparse/tl_out/-_0_0_0/compilation_metrics_2.html

This would especially be useful when checking dynamo_config and would have been useful when debugging https://fb.workplace.com/groups/1075192433118967/permalink/1889257968379072/. While we can also see some of the configs in the fx_runnable and chromium events, 1) we don't have fx_runnable when the backend is not inductor. and 2) it's annoying to have to click into perfetto trace to see dynamo configs.

[angelayi]

nit: I feel like in the past the tlparse code has mostly been structured like, the parser organizes the values from the log files, and then templates.rs contains html/formatting changes such as the heading, and the loop through the dictionary to place it in the html file nicely. Whereas this code just generates an html string

[yushangdi]

sure, modified!