Additional logging for field and content type creation; code analysis message fixes

Main change is some additional logging in field and content type creation.

Was also a duplicate change in mail utility logging (someone else had also fixed the code analysis messages)... but the previous fix didn't pass parameters correctly to the logging methods: 
 - if logging an exception put it before the message, and it will be correctly appended and formatted
 - otherwise, if it is put after the message, then it is treat as an argument for formatting, i.e. there has to be a corresponding "{0}" in the format string to output it. (This is seen in the verbose logging of the rethrown exception).
 - also, not everything should be logged as error, e.g. the cancel is better logged as a warning (its not an error), and the rethrown exception logged as verbose (because it will be logged elsewhere as an error, i.e. when caught).