Add :pylint: Sphinx role for referencing messages

[Br1an67]

Closes #10563

Type of Changes

	Type
✓	✨ New feature
✓	📜 Docs

Description

This PR adds a custom Sphinx role :pylint: that allows easy referencing of pylint message documentation throughout the documentation. The role automatically determines the message category (error, warning, convention, refactor, information, or fatal) and generates appropriate links to the message documentation pages.

Usage

To reference a pylint message in documentation:

:pylint:`used-before-assignment`

This will create a link to the message documentation page at user_guide/messages/{category}/{message-name}.html.

Implementation Details

• Created a new Sphinx extension doc/exts/pylint_role.py that implements the custom role
• The role uses a cached mapping of message names to categories for performance
• If a message name is not found, it displays a warning during the Sphinx build but still creates a text node (graceful degradation)
• Added the extension to the list of Sphinx extensions in doc/conf.py
• Created a changelog fragment documenting the new feature

Files Changed

• doc/exts/pylint_role.py - New Sphinx extension implementing the :pylint: role
• doc/conf.py - Added pylint_role to the extensions list
• doc/whatsnew/fragments/10563.feature - Changelog entry for the new feature

Benefits

This feature makes it easier to reference pylint messages in documentation, especially useful for:

• Changelog entries that reference specific message changes
• Documentation that explains related messages
• Cross-referencing between message documentation pages

[Pierre-Sassoulas]

This already work with :ref `message-name`

See https://github.com/pylint-dev/pylint/pull/10568/changes