Add type checking for numeric kinds

[vezenovm]

Aim

The following code should fail with a type mismatch error:

fn foo<let N: u32>() -> u64 {
    N as u64
}

global J: u64 = 10;

fn bar<let N: u64>() -> u64 {
    foo::<J>()
}

global M: u64 = 3;

fn main() {
    let _ = bar::<M>();
}

Expected Behavior

I expect the code above to fail that we expected a u32 for the numeric generic being passed to foo. The function foo's numeric generic N has a numeric kind with an inner type of u32. This should be type checked against the global J's type of u64 and result in an error.

Bug

The code snippet above passes without error.

To Reproduce

1. Run nargo compile on the snippet above

Project Impact

Nice-to-have

Impact Context

This is not a blocker for using numeric generics but developers could inadvertently use incorrect types which can lead to other bugs or confusion. We should still look to resolve this as soon as possible.

Workaround

No, aside just the developer themselves just passing the correct types.

Workaround Description

Additional Context

This may become a bit easier as part of (#5156) where we are already expecting to generalize the kind check inside of resolve_type_inner.

No response

Installation Method

None

Nargo Version

No response

NoirJS Version

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response