Add a github action for checking binary size on evergreen-arm platforms

[niranjanyardi]

Issue: 441531382

Add a github action to the evergreen-rdk workflow to check binary size regressions

[niranjanyardi]

@isarkis mentioned that it might be better to have the build action run this additonal step instead of having an additional action which requires downloading the output of the github build artifacts .

What do you think @kaidokert ?

[kaidokert]

Wouldn't you want to do this for modular builds as well as a ground truth / reference ? E.g. sometimes Evergreen builds grow for Evergreen specific features. Modular builds would represent more as to what goes into the lib.

[niranjanyardi]

no harm in adding , i just added it to the minimum number of platforms i thought will be useful- evergreen-arm.
ill add it for linux-modular as well

[niranjanyardi]

@isarkis mentioned that it might be better to have the build action run this additonal step instead of having an additional action which requires downloading the output of the github build artifacts .

What do you think @kaidokert ?

talked offline, we are creating a spearate job. this should eventually scale to more metrics on the chrome perf dashboard: https://chromium.googlesource.com/chromium/src/+/HEAD/tools/binary_size/README.md#resource_sizes_py