Method references which aren't immediately invoked can't be mapped due to overload resolution failure #1
Description
Bug
If a method is not immediately called, but rather assigned to a variable or passed as an argument and then invoked later, the method won't be included as a dependency as it will failure during overload resolution using the current mapping process.
The MethodReferenceNotInvoked and MethodReferencePassedAsArgument tests in MethodDependencyMapperTests are currently being skipped as they fail due to this issue.
Possible Solution
When overload resolution failures, attempt to get the correct symbol manually from SymbolInfo.CandidateSymbols.