Change issue title to match allocation in ATL.

Is Grabbiter the device from GLK we want to represent all of GLK?

In general we only need one representative in the CQ for a given SOC family, and it tends to be whatever one is most common or easily obtained, or available earliest. To some extend this choice should be driven by the reference design owners.

From a deployment perspective, we just need to ensure we have sufficient additional devices allocated to support the CQ pool. 

Actually turning on the CQ for these is a matter of two CLs on chromite, one to add them (to verify they work) and one to make them important (so they actually block bad CLs).

+ Vineeth, + Blair to provide guidance on CQ allocation for Octopus devices.

@Bernie - we are using Phaser360 as our "lead." If you need extra devices to allocate, grabbiter is almost the same as phaser360, just a different ODM/OEM.

I think either would be fine as long as it has the superset of the features, so I would say whatever device we think we can easily get the extra allocation for.