Issue #1105: When building the Household Name, always sort the assigned Primary_Contact first regardless of the HouseholdNamingOrder value on the Contact.
Issue #1105: Fix errors in unit tests caused by change to the new sort order of using the Primary Contact first.
Issue #1105: Fix another error in unit tests that only shows up in the final build.
Merge remote-tracking branch 'force2b/feature/1105-primary-contact-first-in-hh-naming' into feature/1105-primary-contact-first-in-hh-naming

Conflicts:
	src/classes/ACCT_HHAccounts_TEST.cls
Merge pull request #1128 from SalesforceFoundation/feature/1105-primary-contact-first-in-hh-naming

Issue #1105: Sort Primary Contact first for automated household naming
Merge dev into feature/1063-require-households-3.1