Track binary sizes for each Yew release

[jstarry]

We should have a good idea of what binary size a user can expect from the framework.

Maybe a table with columns for stdweb and web-sys and rows for various project / feature (services, agents, etc) complexity configs

[voidpumpkin]

I recon we could just track bundle sizes of all the examples. This way we don't need to maintain any separate code for bundle size checking.

[siku2]

I recon we could just track bundle sizes of all the examples. This way we don't need to maintain any separate code for bundle size checking.

I like that idea. Also provides a way to compare sizes across different workloads

[voidpumpkin]

@siku2 js-framework-benchmark now includes binary size tracking so we can just use that from the updated benchmarks action that i will push some time in the future