feat: add new maxes

[PaulRBerg]

Useful for fuzzing timestamps in Foundry tests and bounding them to max uint40 and the maximum value that a Unix timestamp can have (year 2038 problem).

e.g. in practice:

https://github.com/sablier-labs/v2-core/blob/76e29fee33befaeb54a82473c28cf182e6f8855d/test/integration/fuzz/lockup-linear/createWithDurations.t.sol#L57

https://github.com/sablier-labs/v2-core/blob/76e29fee33befaeb54a82473c28cf182e6f8855d/test/utils/Constants.sol#L6-L13

[mds1]

Hm why is this one relevant for solidity devs? I'd think UINT32_MAX would be more appropriate, since I don't think may devs are storing timestamps as signed ints (this value equals type(int32).max)

[PaulRBerg]

What I said in the OP - bounding fuzzed values so that they correspond to real-world values. Unix timestamps cannot go higher than 2^31-1

This isn't about signer or unsigned ints.

[mds1]

Sorry for the slow response here. Thinking about this more, I'd prefer to close this PR. The existing constants are there because they're needed by StdUtils functions, and these are not used anywhere in the StdUtils methods.

Base.sol is where constants are defined for user consumption, and even then I'd prefer to keep that minimal, and only add values that are not exposed in modern solidity (e.g. as you know type([u]intN).max is supported, making the constants not needed for most users anymore).

Going to close optimistically as part of the triage I'm doing now, but of course still open to further discussion even if the PR is closed :)