Pin numba version

[vyasr]

Description

Changes in the upcoming numba 0.57 release will break cudf until we've had time to adapt them, which will not happen in 23.04.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[gmarkall]

There were some CUDA-related fixes for extensions that went into Numba 0.56.4 - while we're here could / should we bump it to >=0.56.4,<0.57?

FWIW, <0.57 looks like the correct upper bound to me from a Numba standpoint but I can't vouch for the changes (whether there's other locations that need changing in cudf).

[bdice]

@gmarkall @brandon-b-miller @vyasr Can we cross-link an issue describing the problem with Record types / UDFs? Anything to document why we’re pinning in a little more detail, so that we can resolve it later when 0.57 is out and have everything link together.

[gmarkall]

@bdice Created in #13002 to record the general idea - I don't have a working cuDF environment right now so the issue doesn't have e.g. the traceback and a complete environment description attached, but the problem is well-understood.

[gmarkall]

LGTM (from the perspective of the Numba version ranges).

[vyasr]

/merge