Split from  https://crbug.com/693709 , which was about LLD's /guard:cf support.

LLD currently does not separate out the import address table (IAT) used for delayload support. I wasn't able to understand what the Microsoft linker does here. If LLD sets the DLL characteristic bits to claim that we support delayload IAT protection, binaries crash on startup, so LLD is clearly not doing something that it should be doing.