CRM-15595 - Individual sub-type custom fields don't appear in online event registration

https://issues.civicrm.org/jira/browse/CRM-15595
CRM-15611: fix send copy for case activity
Merge pull request #4576 from yashodha/CRM-15611

Tested, works fine
Merge pull request #4572 from atif-shaikh/CRM-15595

CRM-15595 - Individual sub-type custom fields don't appear in online eve...
CRM-15595 indentation fix

----------------------------------------
* CRM-15595: Individual sub-type custom fields don't appear in online event registration
  https://issues.civicrm.org/jira/browse/CRM-15595
Merge pull request #4577 from monishdeb/CRM-15595

CRM-15595 indentation fix
Encourage better scoping of js CRM vars with new addVars method
Merge pull request #4509 from colemanw/addVars

Encourage better scoping of js CRM vars with new addVars method
--CRM-10206, reverted back some changes that caused regression when creating multi value custom field value using api
--CRM-10206, added api test
Remove redundant help link
CRM-15621 - prevent fatal on payment updates with Auth.net IPN

----------------------------------------
* CRM-15621:
  https://issues.civicrm.org/jira/browse/CRM-15621
CRM-15622: Fix for incorrect Fee Amount.

There's a bunch of fee_amount fields in this section of the code leading
to a lot of confusion (see CRM-15372). Many of the payment processors set
the fee_amount field in the result array they return which sets up the
contribution.fee_amount field, but the Authorize.Net AIM API doesn't
return fee information, so Authorize.Net doesn't set this field. Instead
of setting this field to 0 there, I thought it would be better to not
require that the payment processor set this field. Since some of the
payment processors return the same array that was passed into them and the
payment processors don't need the fee_amount field as an argument, I think
that setting that to NULL before passing it in gets us the correct output.

Note that we still need the fix from CRM-15372 to get the
participant.fee_amount field set correctly because the code that sets up
the pariticpant shares the field array that the contribution creation
uses even though they don't have the same 'fee_amount' field.
Update version to 4.5.5
CRM-15625 - Add support for contribution api honor_type_id param
Merge pull request #4591 from colemanw/CRM-15625

CRM-15625 - Add support for contribution api honor_type_id param
Merge pull request #4586 from giant-rabbit/CRM-15622

CRM-15622: Fix for incorrect Fee Amount.
CRM-15552 Field communication_style not available to be added to profiles
optimised modification
CRM-15630 - ensure social media links work in email messages.

----------------------------------------
* CRM-15630: Petition add signature thank you email doesn't send correct social networking links
  https://issues.civicrm.org/jira/browse/CRM-15630