CRM-15259 use same method to determine whether to show updateBilling link as whether to allow access to form
update fix for bug CRM-15268
CRM-15317: full fix
CRM-15342 - Fix survey type options link
-- CRM-15055, Fixed CRM test for membership batch create

----------------------------------------
* CRM-15055: Line item for membership entity should be created even when Record Payment is not checked
  https://issues.civicrm.org/jira/browse/CRM-15055
--HR-379 Fix notices coming while importing relationship details
CRM-15351 relationship report: filter contact type on contact table
Merge pull request #4199 from pradpnayak/CRM-15055

-- CRM-15055, Fixed CRM test for membership batch create
Merge pull request #4206 from colemanw/console

Fix safety check when using window.console and switch to console.warn for warnings
Merge pull request #4208 from lcdservices/CRM-15351

CRM-15351 relationship report: filter contact type on contact table
CRM-15242 - Resubmit PR #4103
Merge pull request #4209 from colemanw/CRM-15242

CRM-15242 - Resubmit PR #4103
Fix accidental breakage of CiviMailUtils
CRM-15341 - D7 hack to get the toolbar out of the way

We shouldn't have to do this, but for the sake of our UX here's a hack
to fix the incompatability between the Drupal toolbar and jQuery UI.
Merge pull request #4210 from colemanw/CRM-15341

CRM-15341 - D7 hack to get the toolbar out of the way
Common.js - minor cleanup
Webtest cleanup and fixes
Merge pull request #4205 from NileemaJadhav/CRM_HR_45_test

--HR-379 Fix notices coming while importing relationship details
Webtest fix
INFRA-124 - tools/scripts/phpunit - Add error check

The goal is to eventually switch from the embedded phpunit
("civicrm/packages/PHPUnit") to a more standard/standalone copy.  Howeer,
this requires a different CLI (e.g.  "./scripts/phpunit CRM_Foo_BarTest" vs
"phpunit tests/phpunit/CRM/Foo/BarTest.php").

When we make the switch, we'll need some kind of transition for developers
who use the old CLI. This commit provides them with a better error message.

Note: It's tempting to automatically call the standalone phpunit rather than
printing an error; however, there are edge-cases (like unit-tests for
extensions) to consider, and (for now) it's easier to just throw an error
rather than try to think through each of them.