Move `lvcnrcheck` error messags to `format` implementation
The current error message logic is handled between
lvcnrcheck and the
format implementation. It is also restrictive in that only 4 possible errors can be handled with hard coding of error pathways for specific errors.
The objective of this PR is to refactor
lvcnrcheck to accept a general
(<error-code>, <error-msg>) tuple, and move all specifics of errors (specific codes and messages) to
format, where an unrestricted spectrum of such tuples can be returned even as far as custom tuples for each field.