Install tzdata-legacy when building extra docker image

[TrayanZapryanov]

Describe the Problem

Once developers migrate from jammy:8.0 to runtime:9.0.0-noble-chiseled-extra, they can experience incompatibility issues with time zones.
Suggestion in 6072 was to install tzdata-legacy or to force ICU changing their stuff.

Describe the Solution

Install tzdata-legacy in extra image to prevent breaking changes.

Additional Context

See 6072 for more context.

[lbussell]

Thank you for the feature suggestion. The easy path for users being able to add tzdata-legacy to their own Chiseled images is going to depend on:

• Adding tzdata-legacy slice to https://github.com/canonical/chisel-releases
• Update Chisel to v1.0.0 #5973
• Need sample that shows the installation of additional packages in chiseled scenarios #4811

#4811 is the biggest unknown - if it turns out that adding packages to existing Chiseled images is still difficult/extra even after Chisel v1.0.0, then we could consider adding tzdata-legacy by default to noble extra images.

And just to be clear, @TrayanZapryanov, are you actually hitting this issue with Time Zone ID incompatibility today?

[TrayanZapryanov]

Yes,
Logs in previous issue were from production environment. At the moment they are not so much to rever to .net8 as only half of the customers are affected.

[mthalman]

• Adding tzdata-legacy slice to https://github.com/canonical/chisel-releases

I talked with @rebornplusplus about this. This is being investigated.

[richlander]

Do we have a size cost for tzdata-legacy? I am guessing it is a drop in the bucket compared to ICU.