Introduce common enum/format column exception

[stewSquared]

Often, a failure when parsing a string from a database column indicates not an expected bad input, but some sort of inconsistent or illegal state in the database, since data is validated on the way in (by convention). This happens so often over all our EntityRowConversion traits, that independent helper methods .

In referrals:

  private def expectValid[ADT](fromString: String => Option[ADT], column: String)(
      implicit adtClass: ClassTag[ADT]): ADT = {
    fromString(column).getOrElse(throw new DatabaseException(s"corrupted value found for $adtClass: $column"))
  }

In payments:

  def useFromStringToConvertOrDie[T](converter: { def fromString(s: String): Option[T] }, fieldValue: String): T =
    converter.fromString(fieldValue).getOrElse(throw new IllegalStateException("Unrecognized field value."))

In advocates:

  def entityFromString[T](entityStr: String, mapper: (String => Option[T]), entityName: String): T =
    mapper(entityStr).getOrElse(throw DatabaseException(s"Invalid $entityName in database: $entityStr"))

Elsewhere, ad-hoc Exceptions (not necessarly ServiceException) are thrown, and in far too many places, we skip error reporting altogether and fill in fake data, or otherwise hide the distinction between error and optional states:

  email.flatMap(Email.parse).getOrElse(Email("not", "set"))`

Let's put something into xyz.driver.core.database and standardize. I recommend the first snippet with possible renaming.

See also the more specific case of UUIDs: #82

[stewSquared]

Resolved by #109