Log DB exceptions on SiteDBEditPage

SiteDBEditPage is smart, and rolls back failed DB calls, showing the user a "something went wrong" message. However the exception is just thrown away by default. This means we never get reports of failed queries, and makes development tricky. So instead always process the exception and continue so it gets outputted in development, and logged in production.
prepare for release of 2.1.19 | package party
Merge pull request #94 from isaacgrant/sitedbeditpage-log-db-exceptions

Log DB exceptions on SiteDBEditPage
Allow for no message to be added.
Merge pull request #96 from charleswaddell/hide-account-password-message

Allow for no message to be added.