SDK: Add telemetry library support for the /authenticate API request

[rtamalin]

Leverage the /authenticate API request (#3) to implement authentication support in the telemetry library.

A client will use the /authenticate API request for one of the following reasons:

• to check that the existing auth token is still valid.
  • e.g. AuthenticationStatus()
  • potentially can also be used to check if telemetry client has been registered?
• to obtain an updated auth token as the existing one has expired
  • e.g. AuthenticationExtend()
• to obtain an updated auth token because the existing one is no longer valid
  • e.g. AuthenticationRenew()

The headers of the re-authentication request must include the following items:

• client id
• SHA256 of the existing authentication token

The payload of the re-authentication request contains the following items:

• SHA256 of the client instance id
  • optional, only required if a client is requesting a new token because the existing one has expired or is no longer valid

The telemetry client will be responsible for storing the updated authentication token so that it can be used in future requests.