fix(consumption-profile): use family and TDP parameters in CPU completion

[Shillaker]

Problems

The CPU consumption profile endpoint:

• Does not currently use the family and TDP parameters from the name completion
• Returns a 500 error if the CPU name fuzzy-match fails

Fix

• Use all relevant values from fuzzy matching to compute consumption profile
• Tolerate unrecognised CPU name (by taking the default)