feat(task-service)!: add spec compliant task service support

[jayzhudev]

Adding this support for RMS firmware upload status checks.

Breaking change:

• When the task-service feature is enabled, the redfish::Error now has 2 new variants.

[poroh]

If I understand correctly then it is from Location header from the result of the operation. It would be nice to:

1. Introduce type for a Location header value
2. Use it here and task service should check that Location header value corresponds to its own odata.id.

This will express additional knowledge trough type system and better errors if somebody by mistake will use task service for non-task values (I think some vendors may have their own async job services, see Dell OEM jobs for example).

[poroh]

Maybe we also should add separate function that can check that Location is valid Task resource.

[jayzhudev]

This is a very good and thoughtful call, thanks!

After some thinking, I see two options here:

1. add a Location type. The intent is clearer to the caller but it wouldn't prevent caller mistakes of calling a wrong task service instance - we would still need validation in task calling.

2. keep the API simple and only add validation inside TaskService::task(). The caller passes the task path, and TaskService checks it is under the BMC's Tasks collection before polling.

Option 2 seems to have the right tradeoff to me because the validation is task-specific, and TaskService already has the Tasks collection needed to do it.