feat(service): add a consolidated get of memory resource block statuses

[scott-howe-1]

This changes gives the frontend client the ability to update the composition status of all blade memory resources blocks in a single call (BladesGetResourceStatus())

Statuses are returned as a collection:

type BladesMemoryResourceStatusCollection struct {
	StatusCount int32 `json:"statusCount"`
	ResourceStatuses []BladesResourceStatus `json:"resourceStatuses"`
}

with an array of statuses, with each element looking like:

type BladesResourceStatus struct {
	Uri string `json:"uri"`
	Id string `json:"id"`
	CompositionStatus MemoryResourceBlockCompositionStatus `json:"compositionStatus"`
}

and

type MemoryResourceBlockCompositionStatus struct {
	CompositionState string `json:"compositionState"`
	MaxCompositions int32 `json:"maxCompositions,omitempty"`
	NumberOfCompositions int32 `json:"numberOfCompositions,omitempty"`
}

This "status" struct can be expanded to include more information in the future. Currently, though, it's just reporting composition state information.
Curl output example:

When the blade is running legacy BMC code that does NOT provide a consolidated resource block status response, an empty collection is returned. This will indicate to the client that they need to retrieve the status information one blade at a time via the BladesGetResourceById api.
This behavior is for backward compatibility and is not the intended behavior going forward.

Additional frontend API's were also added for being able to report similar status information for blade-memory, blade-ports and blades. These have been left Not Implemented for now.