CRM-14798 - better fix for lock icon markup.

----------------------------------------
* CRM-14798:
  https://issues.civicrm.org/jira/browse/CRM-14798
Merge pull request #3589 from davecivicrm/CRM-14798a

CRM-14798 - better fix for lock icon markup.
Merge pull request #3582 from totten/master-auto-reconcile

CRM-14786 - CaseType - Perform reconciliation whenever a case-type definition changes
CRM-14798 - crmUi - Add "goto()" helper function

Example: <button ng-click="goto('home')">Go home!</button>

This allows us to use buttons instead of <A HREF>'s -- which makes it easier
to maintain consistent styling in a button bar.
CRM-14798 - civicrm.css - Styling for disabled buttons
CRM-14798 - crmCaseType/edit.html - Only allow saving of valid forms
CRM-14798 - crmCaseType/timelineTable.html - Fix validation of hidden fields
CRM-14798 - crmCaseType - Fix handling of labels+validation

In our UX, labels are supposed to turn red when a field becomes invalid, and
they're supposed to include a red "*" if required.  This adds an Angular
directive to enforce both.
CRM-14798 - civicrm.css - Apply ng-invalid styling for <input>s but not <form>s
CRM-14798 - caseTypeDetails.html - Display warning when changing caseType.name
Smart Group Notice Fix
Merge pull request #3591 from jitendrapurohit/SmartGroup_Notice

Smart Group Notice Fix
Merge pull request #3558 from atif-shaikh/CRM-14782-fix

CRM-14782 fix
CRM-14927 - Batch update via Profile - copy icon fails for fields of 'select' type

https://issues.civicrm.org/jira/browse/CRM-14927
Merge pull request #3592 from atif-shaikh/CRM-14927

CRM-14927 - Batch update via Profile - copy icon fails for fields of 'se...
Merge pull request #3590 from totten/master-crmCaseType-validate

CRM-14798 - crmCaseType - Validation fixes
CRM-14798 - CRM_Case_XMLRepository - Don't double-munge the case-type name.

Prior to this commit, the naming for a case-type flowed more or less
like:

1. User makes up a display-name (title/label)
2. That title is munged via CRM_Utils_String::titleToVar to produce a machine-name
3. That machine-name is munged via CRM_Case_XMLProcessor::mungeCaseType to produce a file-name

As we begin allowing more varied dataflows for managing CaseType XML files
and CaseType DB records, it becomes more important for the naming behavior
to intuitive.
CRM-14798 - crmCaseType - Filter/validate caseType.name

If the name is auto-generated, filter out invalid characters. If the name is
manually-generated, emphasize errors.
CRM-14798 - XMLRepository - Load XML files using the real type name *or* the double-munged name
CRM-14798 - CRM_Utils_Check - Display warning if site has mismatched file names