Angular patron editor post-2.10 misc. bugs

Evergreen 2.10.1

Omnibus branch en-route to resolve the following angular patron editor issues:

1. Avoid warning on duplicate username when the username is owned by the patron being edited.

2. When a username regex is present, consider both regex-compliant usernames and an equal match on the barcode as valid usernames, even if the barcode is not regex-compliant. (It usually isn't).

3. Instead of disabling the Save buttons, allow the user to click Save or Save/Clone when invalid fields are present, but display an alert (and prevent save) instead. This is consistent w/ the XUL client and better clarifies why the action is not allowed.

4. Allow all addresses to be deleted on a user unless the org unit setting for requiring an address is true.

5. Misc. repairs to enforcing required fields. Of note, county and state specifically are required now if the matching org setting is true.

6. Consistent (small) sizes of checkboxes for boolean fields -- they done got real big.

7. Removing the last address should not hide the New Address button. It should always be visible.

8. Linked addresses should not be editable from the cloned account. Only the lead account.

9. Only attempt to save stat cat values for stat cats that are within scope.