feat: setup size-limit report and define size budget

[danisharora099]

This is a feature request.

Problem

Right now we don't have any strategy for measuring and limiting size of js-waku package family.

Proposed Solutions

Define maximum size limit for the packages in js-waku and re-configure size-limit config to check entry points of the packages and warn in PRs about violation.

Notes

Running time from the size-limit report to be investigated as it doesn't seem as deterministic metric.

[danisharora099]

• republish/move the size-limit script to a more accessible location
• remove the fields that are not as useful (running time, etc)
• look at coverage

[weboko]

Quickly checked it and want to understand: why do we use custom action here?

@fryorcraken

[fryorcraken]

Quickly checked it and want to understand: why do we use custom action here?

@fryorcraken

Because of this: andresz1/size-limit-action#84

[weboko]

Sharing basic knowledge on the size-limit here:

• right now we have test some entry points defined here;
• size limit allows us to define some budget - here;
• underseas it just runs exposed entry points and tests size / running time;

fyi @waku-org/js-waku-developers

Having said that I am reshaping this issue to be part of #337 (updated body of the issue)