1. publish a net5.0 Blazor WASM app. Inspect the bin\Release\net5.0\publish\wwwroot\_framework\dotnet.timezones.blat.br file size. It should be around 66 KB.
2. publish a net6.0 Blazor WASM app using the latest runtime. Inspect the bin\Release\net5.0\publish\wwwroot\_framework\dotnet.timezones.blat.br file size. It is 90 KB.

We should verify if this size increase is expected, and it is warranted.

We should be able to trim a decent amount of data out of this file. The way the IANA timezone database works is that it contains every base time offset transition from the beginning of time, until about 2038. We should investigate if we can only include daylight savings transitions between certain dates. For example, we could only include transitions from 1970 - DateTime.Now + 10 years. This should trim a lot of transitions that are not going to be used.

Another (probably bad) idea would be to use the Windows time zone data instead. This data is less accurate, but is definitely smaller.

You can see the regression at https://aka.ms/dotnetperfstatus

cc @tqiu8