Description of problem:
"syspurpose compliance" and the "subscription compliance" are sharing the same "compliancestatushash" column in the cp_consumer table so after calculating the syspurpose compliance, Candlepin will replace the column with its digest

Version-Release number of selected component (if applicable):
All versions of candlepin that support system purpose so far

How reproducible:
100%

Steps to Reproduce:
1. Register a client
2. Set a syspurpose attribute on the client (e.g. role)
3. Check the database column cp_consumer.sp_status_hash for that consumer

Actual results:
It is null

Expected results:
It should contain a hash value

Additional info:
The offending code is here: https://github.com/candlepin/candlepin/blob/50b7144dc13c9688add43c3e716851f6430e5dfc/src/main/java/org/candlepin/policy/SystemPurposeComplianceRules.java#L274-L277
the getSystemPurposeStatusHash/setSystemPurposeStatusHash methods should be used instead.