Re-adding missing commit which adds some theming and handling of payment profiles for CIM. This commit was in 43a42d66 but somehow got wiped out in a merge?

Do not allow $account to be specified more than once when loading AuthorizenetProfiles and AuthorizenetPaymentProfiles.  This was creating some cute assumptions that the current user's details should be accessed - and not those of the activity owner.

Clean up processing of profile transactions to make sure they work with re-submissions (e.g. authorize+capture and/or just 'capture')

Respect this activity as a CIM activity if the activity history includes CIM.  This means that a 'complete' activity for an 'authorize' or 'pending' CIM activity will respect the previously-selected profile and user.

The CSV results for a transaction are not returned when there's an error.  This was causing any XML failures to return as 'successful'.  

Correctly parse the XML response AND the CSV data.

Implement pending_action, which allows transactions to occur even if the requested action is 'pending'.  This allows CIM to collect information for later processing.

Ensure that the relationship between activities and payment profiles is always stored, even when there's no transaction request.

When collecting but not processing CIM payments, ensure that we're storing enough data to effect the transaction later:

Create a table that stores a relationship between a payment profile and every activity it participates in.

Conflicts:
	includes/handlers/pay_method_gateway_authorizenet.inc

Restore full functionality to the AIM handler using the data structure for the underlying Authorizenet and AuthorizenetTransaction classes.

This allows us to set up a usage-agnostic $transaction and process it with any backend, now including CIM and AIM.

Pass in and store a user account on an Authorizenet instance.  This permits access to user->mail, user->uid, etc. during payment transactions.

Store configuration settings on Authorizenet instances:
 emailCustomer
 emailMerchant
 testMode

Remove authorizenet_trxtype from main pay_method handler, as it really only applies to AIM transactions

Fixup AIM transactions to handle the new data formats.

Suddenly, TRUE/FALSE is causing the API to start throwing errors. Using true/false for boolean values.

Augment the paymentProfiles() method for AuthorizenetCimProfile instances so that it can augment the local data with data that is stored in the CIM.  This validate the existence of these entries, and allows us to show values we're not showing locally, e.g. address info.