Where applicable, MgFdoExceptions should be thrown with associated Feature Source information

[jng]

The key motivation for this ticket is #739

As is obvious from that particular ticket, sometimes we need to know the Feature Source ID that is associated with a thrown MgFdoException in order to better diagnose the problem.

Currently all these exceptions are thrown through an intricate set of pre-defined macros that do not include the feature source id.

The solution is to offer an alternate set of macros that take an MgResourceIdentifier, and where applicable in MgServerFeatureService, use these alternate macros instead.

[jng]

With the attached patch where applicable, errors that were:

An exception occurred in FDO component. <message>

Now look like this:

An exception occurred in FDO component. Error occurred in Feature Source (<feature source id>) <message>

[jng]

Fixed in trunk (r6715) and 2.4 (r6712)