CI/DEP: Use numba.extending.is_jitted for numba version > 0.49.0

[mroeschke]

• xref BLD: Set max version of numba to 0.48.0 #33686
• tests added / passed
• passes black pandas
• passes git diff upstream/master -u -- "*.py" | flake8 --diff

[jreback]

lgtm merge on green (are we testing <0.49 anywhere? maybe fix it in one of the older builds)

[mroeschke]

azure-36-minimum_versions.yaml is testing numba = 0.46.0, so we should be covered

[simonjayhawkins]

@meeseeksdev backport to 1.0.x

[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 1.0.x
$ git pull

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

$ git cherry-pick -m1 e0d4622cb7189adba8fc65571ff5a608564f8c67

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

$ git commit -am 'Backport PR #33687: CI/DEP: Use numba.extending.is_jitted for numba version > 0.49.0'

4. Push to a named branch :

git push YOURFORK 1.0.x:auto-backport-of-pr-33687-on-1.0.x

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

"Backport PR #33687 on branch 1.0.x"

And apply the correct labels and milestones.

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

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