Add linter and guard, apply fixes and suppress by scope

[WalterWoshid]

Mago inspection now runs lint and guard together with analyze and shows all results in the editor. You can apply Mago autofixes from annotations and suppress issues by statement, function, method, or class. Fixes and suppress actions support intention preview (Ctrl+Q).

Changes

• Linter and guard – When enabled in settings, the pipeline runs mago lint and mago guard in addition to analyze and merges problems into the same annotations. Lint and guard issues get the same apply-fix and suppress quick fixes as analyze.
  

• Better descriptions
  

• Apply fix – Apply a single Mago autofix from the problem annotation (Alt+Enter). Fix text uses issue help or message, prefixed with "Mago: ". Before there was a global "Mago: fix the whole file", which only ran the formatter. This has been removed.
  

• Apply all by safety – Submenus: "Fix all (safe only)", "Fix all (potentially unsafe)", "Fix all (unsafe)". Each applies only that tier; apply-all uses in-memory edits (no CLI run) so undo works.
  

• Mago: Ignore/Expect – Quick fix to add @mago-ignore/expect category:code with options: for statement, for function, for method, for class. Submenu when multiple apply. Same-category codes merged into one comment.
  

• Ignore/Expect appends correctly to an existing comment
  

• Mago: Navigate to cause - Places the cursor to the problem (works with problems that are reporting in other files!)
  
  

• \Mago\inspect(...) support
  
  
  

• Improved debug notification
  

• Format after fix option - Runs the formatter after applying a fix.
  

• Workspace mappings - Multiple workspace support
  

• Platform – Target PhpStorm (PS) 2025.3.2, adjust Plugin versions + Docker

Required Mago Changes for optimal usage

• --stdin-input Support - This allows passing the editor file contents to the Mago commands. Why? Because if running it without the option will analyze the unsaved file and the annotations are broken/misplaced. I added fallback without --stdin-input if Mago is used with an older version, but that can be removed in the future and only display an error.

• Baseline ignored when using --workspace fix - When Mago is launched from the plugin (from a remote interpreter) it uses the / working directory and --workspace, but it doesn't correctly resolve the baseline entries. This fixes it.

[WalterWoshid]

This Pull Request also makes #47 obsolete, because it is included.

[xepozz]

Thanks for improving the plugin, but let's make it a bit clear first

[WalterWoshid]

Thanks for the review, will do that tomorrow :)

[zip-fa]

@WalterWoshid hey! sorry for bothering, do you still work on this?

[WalterWoshid]

Hi @zip-fa, I was still working on this #49 (comment) but got distracted in real life, gonna try to continue with this. I can also push a branch with my current implementation if you need it.

[WalterWoshid]

@xepozz I updated the issue description and resolved all your comments!