Consider copy edits to CSV error messages

[noah-schechter]

[Not a deploy-blocker] Right now, the error message for blank-but-required attributes looks like this:

I think we should make sure we match the formatting of the attribute names in the documentation, meaning we would change attr_description to description by 1) adding a badge and 2) removing the "attr_" prefix.

For example, the updated message would like:

• Row 1
  description: can't be blank.
  sensitive: can't be blank.
  status: can't be blank.

Longer term, we can add more friendly messages, but for now I just want to make sure the attribute naming system matches what the system expects.

[noah-schechter]

For example, later on we should fix present our own error message for internal errors like this one:

Escape sequence started on line 338: [User-inputted text] Comments: did not terminate. Parsing will continue on line 339. Escape sequences are allowed to span up to 10 lines. This threshold avoids collecting the whole file into memory when an escape sequence does not terminate. You can change it using the escape_max_lines option: https://hexdocs.pm/csv/CSV.html#decode/2

[milesmcc]

[noah-schechter]

This looks great, thanks!