Support for northbound Redfish interface

[jcleung5549]

Add ability to interaction to with Device Manager via a Redfish interface. Minimal support would include

• Chassis, Systems
• AccountService, SessionService, TaskService, EventService

[jcleung5549]

Use cases:

1. Obtain inventory with the Chassis and Systems resource
2. The AccountService, SessionService, TaskService, EventService is to pass the Redfish Service Validator (I will confirm)

[HWAymyra]

Please ensure that the northbound interface should conform to the OpenRMC v1.0 profile first. Once OpenRMC v1.1 comes out, need conformance to it as well later.

[jcleung5549]

2/22 meeting - open separate issue for OpenRMC v1.0 conformance.

• issue for group operations
• issue for firmware update
• issue for authorization of manager and managed node

[jcleung5549]

Issue scoped and approved

[jcleung5549]

The Redfish Protocol Validator is the test that looks for AccountService, SessionService and EventService. TaskService is not tested.
The Protocol Validator also tests for the CertificateService, but it is arguable that belongs in the minimum set.

[jcleung5549]

DM Meeting (Mar 8):
Request Arch review for proposed code to be added to the branch.

Tests to run prior to pull request: OCP Conformance Test Suite (Service Validator, Interop Validator w/Baseline Profile, Conformance Validator) and Device Manager tests prior to pull request.

[jcleung5549]

The branch 'redfishapi' has been created for a code submission.

[MaciejMis]

This was fixed with #52