status_details should have a sibling enum attribute

[pagbabian-splunk]

Currently, we have 4 status related attributes: status_id, status, status_code, status_details. not counting http_status which is tied to the spec.

status_details should have a sibling enum attribute that can be defined within specific classes, with a 'See specific usage` description clause.

The example that exemplified this is in the Authentication class where we suggest via description examples, status_details values:
For status_id = "Failure"

USER_DOES_NOT_EXIST
INVALID_CREDENTIALS
ACCOUNT_DISABLED
ACCOUNT_LOCKED_OUT
PASSWORD_EXPIRED

For status_id = "Success"

LOGOFF_USER_INITIATED
LOGOFF_OTHER

Some of these may be common and could be enum values, especially for the Failure cases. In fact, we don't have any normalized way to represent some of these common cases. We would as always still have an Other case.