Add rule for SourceHttpMessageConverter issue

[jmle]

See #156

Supersedes #176

[rromannissen]

LGTM! Great job, this one was super tricky!

[rromannissen]

I think we might have overlooked something here. Even if you follow the guidelines in the snippet and change the configureMessageConverters method to add the SourceHttpMessageConverter to the HttpMessageConverter list, the rule would still be still finding incidents in the same locations regardless of the change.

That means that we need to add an and not condition that contains a pointer to the right configuration (again, adding a SourceHttpMessageConverter to the HttpMessageConverter list inside of an invocation to the configureMessageConverters method inside of a class that implements the WebMvcConfigurer interface).

This feels like a pattern for issues that get solved by a change in configuration, always add an and not condition expressing the right configuration to get the issue solved. @jwmatthews @pranavgaikwad @shawn-hurley @fabianvf I wonder if we could leverage this in Kai to inform the LLM of how to fix issues when the solution is not local to where the incidents were found.