Enable numeric generic inputs for non-inlined ACIR

[vezenovm]

Problem

As part of the initial work to add non-inlined ACIR #4428 we added type checking that treated all inputs to entry point ACIR the same. This meant non-inlined ACIR functions which were not main would have the same restriction of only support what is supported in Noir's ABI. This is an unnecessary restriction.

Happy Case

We should support more compile-time inputs for non-inlined ACIR entry points. For example, numeric generics should be known at compile-time for non-inlined ACIR.

References will still have to be restricted. We would only be able to pass references as inputs if we started to support them in ACIR gen. Slice sizes are technically known at compile time, but not during monomorphization when we have slices whose size is dependent upon witness conditions. For now, we just want to upgrade numeric generics.

Project Impact

Blocker

Impact Context

This prevents being able to not inline functions which utilize numeric generics, such as our poseidon2 hash method:

pub fn hash<N>(input: [Field; N], message_size: u64) -> Field {
        if message_size == N {
            Poseidon2::hash_internal(input, N, false)
        } else {
            Poseidon2::hash_internal(input, message_size, true)
        }
    }

Workaround

None

Workaround Description

No response

Additional Context

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response