Fix backend meshgrid array-like coercion

[FlorianPfaff]

Summary

• wrap the backend facade meshgrid for JAX and PyTorch so array-like and scalar axes are coerced via asarray + atleast_1d
• keep NumPy behavior unchanged while making stricter backends match NumPy's permissive meshgrid contract
• add focused regression coverage for list/range/scalar meshgrid axes

Validation

• reproduced the raw JAX/PyTorch failures locally with meshgrid([0, 1], range(2), indexing="ij")
• compared branch against main: 2 commits ahead, 0 behind

Full project tests were not run because this execution environment cannot resolve github.com to clone the repository.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	32.84s
✅ PYTHON	black	2	0	0	0	1.63s
✅ PYTHON	isort	2	0	0	0	0.45s
✅ REPOSITORY	checkov	yes		no	no	30.24s
✅ REPOSITORY	gitleaks	yes		no	no	16.18s
✅ REPOSITORY	git_diff	yes		no	no	0.04s
✅ REPOSITORY	secretlint	yes		no	no	14.27s
✅ REPOSITORY	syft	yes		no	no	2.41s
✅ REPOSITORY	trivy-sbom	yes		no	no	3.78s
✅ REPOSITORY	trufflehog	yes		no	no	23.84s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

Show us your support by starring ⭐ the repository

[github-actions]

Test Results

    10 files      10 suites   2h 48m 38s ⏱️
 2 170 tests  2 166 ✅     4 💤 0 ❌
22 131 runs  18 340 ✅ 3 791 💤 0 ❌

Results for commit 3bb4575.