Initial work for workflow registry v2: limits

[eutopian]

No description provided.

[github-actions]

Static analysis results are available

Hey @eutopian, you can view Slither reports in the job summary here or download them as artifact here.
Please check them before merging and make sure you have addressed all issues.

[ibrajer]

Not 100% sure on this, but generally, deleting elements in mappings/arrays is avoided due to gas costs, so resetting values is more desirable. Since you're already using this isSet field value, maybe you can just set it false? In that case, this code is as simple as:

s_cfg.userOverride[user] = Config.Value(limit, isSet);

[eutopian]

delete is only costly for large structures, but this is one slot size, so delete versus setting this to false cost the same storage write but has the slight benefit of the cleared slot refund. the only benefit potentially in allowing it is record I think.

[ibrajer]

You could also use the uint32 max value or any other arbitrarily large value to have a special meaning, but this is certainly easier to understand!

[eutopian]

This looks like it's more complicated but actually not much more as both are small and fits into one storage slot, but much more explicit and readable than using an arbitrary value to get around the falsey zeros