Fix bug for logging TaskAssemblyLocationMismatch comment

[YuliiaKovalova]

I think that's because TaskHostTask is always going to be a type loaded from the currently running code--but it wraps a task from some other assembly, which is what we actually care about for this message, right?. Looks like a preexisting bug where we log this for all TaskHostTasks.

Originally posted by @rainersigwald in #11393 (comment)

[JanProvaznik]

this is somewhat worse because of multithreaded effort, because custom and inline tasks will be wrapped as taskhosttasks

[JanProvaznik]

for multithreaded this is still broken