Add # typeprof:disable/enable directive for silencing diagnostics

[smasato]

Overview

This PR adds RuboCop‑style comment directives that let users silence TypeProf diagnostics.

foo(1, 2) # typeprof:disable           # inline – only this line

# typeprof:disable                     # block start
foo(1, 2)
bar(1, 2)
# typeprof:enable                      # block end

The feature works in CLI and **LSP modes

---

Implementation notes

• Diagnostic::DisableDirective::Scanner – parses comments and returns muted line ranges.
• Diagnostic::DisableDirective::Filter – determines whether a diagnostic should be reported.
• ProgramNode#diagnostics applies the filter. I implemented the filtering logic in ProgramNode, but please let me know if there is a better way.

---

Related issue

Closes #108

[mame]

Awesome job, thanks!

Let me think this for a while before merging. I'm a little concerned about whether typeprof:enable is good or not. Also, the amount of changes is relatively large that I want to do a design-level review. This will take some time.

[smasato]

@mame
Thanks for the comment!

I followed RuboCop’s style, so # typeprof:disable/enable only turns diagnostics on or off for that block—it never touches the type‑inference logic itself. That wording might still confuse users, so I’m open to better keywords. Let me know what you think whenever you’re ready.