core: Introduce integer constraints

[alexarice]

This would probably make #3698 obsolete, as it covers the one use case of that PR that I can think of. This is a bit more of an involved change but I feel that there are some interesting a powerful things you could do with this in the future.

Would likely need a few more tests if we want to go with this.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.31%. Comparing base (b83ddb2) to head (6135f83).
Report is 75 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3699      +/-   ##
==========================================
- Coverage   91.31%   91.31%   -0.01%     
==========================================
  Files         467      467              
  Lines       58487    58586      +99     
  Branches     5640     5645       +5     
==========================================
+ Hits        53406    53495      +89     
- Misses       3632     3640       +8     
- Partials     1449     1451       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[math-fehr]

Sorry for the delay, that looks good to me!
Hopefully we can encode some constraints for variadics with it ;)

[alexarice]

@math-fehr the idea was that this is an alternative to #3698, did you have any preferences between the two.

[kimxworrall]

I vote this one as it allows you to have different input and output types in the example given.

[alexarice]

@math-fehr any thoughts? I'm hoping that this version should be able to encode some constraints for shaped types.

[compor]

I prefer this one

[alexarice]

I'll merge this PR in a couple of hours unless anyone else has comments

[math-fehr]

Sorry, I am overwhelmed work-wise recently, so I missed your question!
I do prefer that one :)