trunk/092e9ae55e333ebdd0e0f1751a7bb1fa46736c42: Add a linter on fallback_ops.py to add versioning (#182130)

PyTorch, the popular open-source deep learning framework with 99.6k GitHub stars, has introduced a new linter in PR #182130 that targets fallback_ops.py. This lint enforces that any new operations added to the fallback list include proper versioning information. Previously, versioning checks were performed on the generated shim files—but those are auto-generated, making it harder to trace errors back to the source. By moving the lint to fallback_ops.py, developers now get immediate feedback on where to add versioning tags when introducing new fallback operations.

The change is designed to streamline the contribution workflow and prevent compatibility issues. The PR was approved by key PyTorch maintainers albanD and malfet, signaling strong community support. This update reflects PyTorch's ongoing efforts to improve code quality and reliability, especially as the framework scales to support a growing number of custom operators and hardware backends. For developers contributing to PyTorch's core, this lint will reduce debugging time and ensure consistent versioning across releases.