Token scope and spec scope mismatch error is not clear in logs

[stevehu]

With service to service call, if token is not matched, the error message is not clear when service has the wrong token and what is the token scope and spec scope.

Need to verify that when logs are aggregated in ELK, the service Id which is container name should be indexable.

error response.

{"statusCode":403,"code":"ERR10005","message":"AUTH_TOKEN_SCOPE_MISMATCH","description":"Scopes in authorization token and spec scopes are not matched"}

[stevehu]

Here is the new response captured in test case.

{
  "statusCode": 403,
  "code": "ERR10005",
  "message": "AUTH_TOKEN_SCOPE_MISMATCH",
  "description": "Scopes [ATMP1000.w, ATMP1000.r] in authorization token and specification scopes [write:pets, read:pets] are not matched"
}