Add system token header to query SCC subscriptions (bsc#1219855)

[dirkmueller]

when a system was cloned, SCC falls back to the first system ever registered for determining subscriptions. passing in the system token should help with that.

[digitaltom]

Sorry, I'm a bit late in the game here, but it's important that when authenticating including the system token, to also write back the new token of the response to the credentials file. Else the next API request will use an outdated token and trigger a system duplication on the server.

[dcermak]

Sorry, I'm a bit late in the game here, but it's important that when authenticating including the system token, to also write back the new token of the response to the credentials file. Else the next API request will use an outdated token and trigger a system duplication on the server.

That's not possible from container-suseconnect, as it cannot write to the host's credentials file.

@dirkmueller shall we revert this then?

[dirkmueller]

@dirkmueller shall we revert this then?

No, the change is needed. we're going to change SCC instead.