fix(debugger): restrict line breakpoints

[kopavel]

Summary

Fixes #658.

Restricts RobotCodeLineBreakpointType to Robot Framework .robot and .resource files.

Previously, canPutAt() returned true unconditionally, making the RobotCode line breakpoint type applicable to unrelated files such as C# sources. In Rider this could cause newly created C# breakpoints to be registered as RobotCode breakpoints instead of .NET breakpoints.

Type of change

• Bug fix
• New feature
• Refactor / internal change
• Documentation
• Build / CI / tooling
• Breaking change

Checklist

• I have read the Contribution Guide and the AI and Automated Contribution Policy.
• The change is focused on a single concern (no unrelated refactors or formatting noise).
• Tests for the change have been added or updated, and hatch run test:test passes locally (RF matrix against the default Python) — or N/A for documentation-only / non-code changes.
• hatch run lint:all passes (also enforced by the pre-commit hooks) — or N/A for documentation-only / non-code changes.
• Documentation has been updated where relevant (no documentation changes required).
• Generated files (if any) were regenerated with the documented script, not edited by hand. No generated files were changed.
• Commits follow Conventional Commits and are cryptographically signed.

AI / tooling disclosure

• No AI/automation was used beyond ordinary editor autocomplete.
• AI/automation was used; tool(s): ChatGPT
  • I reviewed the generated output manually, understand it, and verified it locally.

Additional notes

The JetBrains plugin was successfully rebuilt after the change.

The fix was also tested in Rider 2026.2.2 with RobotCode 2.7.0 by replacing the affected compiled breakpoint classes in the installed plugin.

Verified manually:

• .robot and .resource files continue to support RobotCode breakpoints.
• Newly created .cs breakpoints are handled by the Rider/.NET debugger.
• Existing .NET breakpoints continue to work.