feat: add analyzer for direct command handler calls

[meenzen]

No description provided.

[alexyakunin]

Hi, I'll definitely have a look & merge this in a few days. Want to finish with Rpc first.

[meenzen]

In the current state this should be considered a proof of concept. Unfortunately I don't have the time to properly finish this right now.

[alexyakunin]

Hi, still didn't get back to this - a lot of stuff on my plate, but I remember about this.

[alexyakunin]

Hi, I look up the code - couple quick things:

• Let's use "STLC" prefix for the warning ("Stl.Commander")
• I would also check if the call is happening on the interface vs the class. Coz technically class calls might be "ok" (e.g. base method call), + attributes are normally applied to the interface
• Maybe add a test covering a case when such a method is called on a descendant of an interface where it is declared
• Maybe add a test where the interface is declared in external module (i.e. is consumed from an assembly vs compiled).

I suspect there might be issues with two later tests. Overall, the attributes are inherited in Fusion - both from base classes and from the interfaces, so doing a totally correct check is kinda complicated. But covering even the primary case would be nice. That's why I wrote "maybe add a test" - i.e. I think it's good to cover at least these scenarios (they are frequent), as for anything beyond that (e.g. inspecting the whole inheritance chain), I think it's fine to do this in some other step, or even ignore this.

[alexyakunin]

@meenzen please check out my comment above, and sorry for delaying this.