CI: Pin Numba<0.57 in ARM build

[mroeschke]

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[lithomas1]

@mroeschke
I see numba 0.57.0 dropped on conda-forge just under a day ago. Maybe pinning might help?

The segfault comes from test_numba_vs_cython.

[phofl]

thx @mroeschke

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 2.0.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 9d38f40767da08ff46b807fd9565666a7aaf079c

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #53309: CI: Pin Numba<0.57 in ARM build'

4. Push to a named branch:

git push YOURFORK 2.0.x:auto-backport-of-pr-53309-on-2.0.x

5. Create a PR against branch 2.0.x, I would have named this PR:

"Backport PR #53309 on branch 2.0.x (CI: Pin Numba<0.57 in ARM build)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.