REF: speed-up describe using numba

[martinfleis]

Follow-up on #570

Had to reimplement mode to actually compile based on numba/numba#2959 (comment).

Timings compared to #570

only quantiles
# new 2.23 s ± 65.6 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
# old 7.96 s ± 59.5 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

no quantiles, mode
# new 1.25 s ± 7.76 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
# old 15 s ± 488 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

quantiles and mode
# new 2.48 s ± 42.9 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
# old  23 s ± 562 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

How would you set the CI envs to test numba and fallback options? I am not a big fan of having everything twice. Would 1 env without numba be enough in your experience?

[codecov]

Codecov Report

Attention: Patch coverage is 96.29630% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 97.7%. Comparing base (4037c70) to head (5b75742).
Report is 16 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #571     +/-   ##
=======================================
+ Coverage   97.4%   97.7%   +0.4%     
=======================================
  Files         26      35      +9     
  Lines       4328    5099    +771     
=======================================
+ Hits        4214    4984    +770     
- Misses       114     115      +1     

Files	Coverage Δ
momepy/functional/_diversity.py	98.0% <96.3%> (ø)

[jGaboardi]

How would you set the CI envs to test numba and fallback options? I am not a big fan of having everything twice. Would 1 env without numba be enough in your experience?

Yes, I think we can add a note to the README, docs, and wherever else that we strongly encourage installing & using numba. Then perhaps adding a 312-min.yml to the matrix that doesn't include numba.