Fix DIMMCount and CPUCount

[perigrin]

The Device Report sends up a dimms and a cpus properties that list the memory DIMMs and the CPUs respectively. These were intended to replace the older memory and processor properties.

This PR updates the DIMMCount and CPUCount validations to use the newer properties instead of the older one. This entirely deprecates processors and leaves the only the total property being used from the object in the memory property (which currently has no analog in DIMMs).

[daleghent]

{memory: {total: <int in GB>}} can be replaced by summing the value of memory-size: <int in GB> that is present in each dimms member. If a particular DIMM slot is unstuffed, there will be no such member (a recent change; empty members are now elided from the report). So basically, if memory-size exists, add its value to a running summation and when you've added them all up, you should have a number that is equal to what {memory: {total: $value} gives us now.

[karenetheridge]

If processor in the device report is no longer to be used by any validations, it should be removed from the json schema.

The version attribute should be incremented for both validation modules affected here, to be consistent with conventions previously established (consequential changes in code should be indicated by a new version). The database then needs to be updated -- you might as well add on to the add_drive_validations command I just created in #626: set deactivated on the updated validations, then when the new rows are added to the validation table, add those new rows to the Server plan.

Fixed by 92f63a3