Fix issue with excessive memory use by debug and checked jits

Fix issue with excessive memory use by debug and checked jits

In dotnet/coreclr#3051 the jit started calling `eeGetClassFullName` for both
caller and callee handles even when dumping was disabled, passed
this information to the logging messages where previously the caller
and callee were identified via other context, and prepared the full
name dump artifacts for all inline decisions rather than the selective
cases handled previously.

This change caused excessive memory use in some tests.

This change makes the calls to `eeGetClassFullName` conditional on
whether dumping is enabled, and does not require these calls for logging
messages.

Commit migrated from https://github.com/dotnet/coreclr/commit/5e852304f2eff62533e103d706a2604a1e82ab17