smarter about size increases of small data

It doesn't make a lot of sense to fail when going from 150kb to 300kb on git repo size (which is a 100% increase!) for example.

Maybe define some minimum thresholds in bytes in addition to the percentage limits. Make it configurable.

E.g. kick if 100% AND more than 10 MB.

Start by locating the size-increase percentage check and the existing configuration entry points in the JavaScript project. Define how a configurable minimum byte threshold interacts with the percentage limit, and verify that small changes such as 150 KB to 300 KB are not rejected while larger increases still are.

Written by the indexing model from the issue text.