refactor: Add NPY to ruff rules

[hoxbro]

Enable Numpy rules: https://docs.astral.sh/ruff/rules/#numpy-specific-rules-npy

The changes are related to NPY002: https://docs.astral.sh/ruff/rules/numpy-legacy-random/#numpy-legacy-random-npy002

I'm not sure why layout.py is part of datashader.

[codecov]

Codecov Report

Attention: Patch coverage is 67.56757% with 12 lines in your changes missing coverage. Please review.

Project coverage is 88.59%. Comparing base (ebd2561) to head (5394e85).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
datashader/tests/benchmarks/test_extend_line.py	28.57%	5 Missing ⚠️
datashader/tests/benchmarks/test_canvas.py	25.00%	3 Missing ⚠️
datashader/tests/test_tiles.py	0.00%	3 Missing ⚠️
datashader/layout.py	90.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1368      +/-   ##
==========================================
- Coverage   88.60%   88.59%   -0.01%     
==========================================
  Files          93       93              
  Lines       18620    18627       +7     
==========================================
+ Hits        16498    16503       +5     
- Misses       2122     2124       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jbednar]

Looks good, thanks!

I'm not sure why layout.py is part of datashader.

If these algorithms are available elsewhere in a usable form, I'd be happy to import them conditionally when using Datashader's network rendering. Otherwise, where would they go if not here, if Datashader is to support rendering networks?

[hoxbro]

Otherwise, where would they go if not here, if Datashader is to support rendering networks?

I'm not sure. I've never seen it as part of Datashader to support rendering networks. But I don't have any strong opinions about this.