[Build] Update numba version to 0.63.1.

[nascheme]

Purpose

For vLLM to support Python 3.14, we need to use a newer version of numba. Version 0.63 of numba adds support for 3.14.

Test Plan

Run ngram_proposer tests using pytest.

Test Result

The unit tests using ngram_proposer pass.

[gemini-code-assist]

Code Review

This pull request updates the numba dependency to version 0.63.1 across all requirement files. While the change itself is straightforward and the tests are passing, the provided justification appears to be incorrect. The pull request description states this update is for Python 3.14 support, but numba version 0.63.1 only adds initial support for Python 3.13. This discrepancy is a high-severity issue as it misrepresents the capabilities of the updated dependency and may lead to future build issues if Python 3.14 support is assumed to be in place.

[gemini-code-assist]

The stated purpose of this pull request is to add support for Python 3.14 by upgrading numba. However, numba version 0.63.1 does not provide support for Python 3.14; it introduces initial support for Python 3.13. This means the current change does not achieve the stated goal. A newer version of numba will be necessary to support Python 3.14 when it becomes available.

[nascheme]

See the release notes, 3.14 support is explicitly noted.

[nascheme]

I'm not sure of the PR workflow on this project, am I supposed to merge my own PR once approved? There are some CI test failures but my impression is those are not related to this change. I'm going to merge with "main" and that will hopefully re-run the tests.

[DarkLight1337]

Sorry CI was broken for the past few days, let's see if it passes now.

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @nascheme.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

Hi @nascheme, the pre-commit checks have failed. Please run:

uv pip install pre-commit>=4.5.1
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy failing?

mypy is run differently in CI. If the failure is related to this check, please use the following command to run it locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @nascheme.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[Harry-Chen]

Included in #34770.