Add system token to PAYG systems when creating the system

[jesusbv]

Description

For regsharing we are querying for the whole key (login + pass + system_token) PAYG systems do not have a system token, this fixes that situation

Move the instance identifier outside SCC class

Use system token to active product and upgrade, not only announce

Add system_token value to systems without system_token if needed

• Related Issue / Ticket / Trello card:

How to test

Register a BYOS or PAYG instance and it should have system_token populated and the value should be the instance identifier (vmId for Azure, instanceId for Amazon and instance_id for Google)

Activate LTSS on a PAYG system without system_token and should have a system_token with the right value (see above)

Change Type

Please select the correct option.

• Bug Fix (a non-breaking change which fixes an issue)
• New Feature (a non-breaking change which adds new functionality)
• Documentation Update (a change which only updates documentation)

Checklist

Please check off each item if the requirement is met.

• I have reviewed my own code and believe that it's ready for an external review.
• I have provided comments for any hard-to-understand code.
• I have documented the MANUAL.md file with any changes to the user experience.
• If my changes are non-trivial, I have added a changelog entry to notify users at package/obs/rmt-server.changes.

Review

Please check out our review guidelines
and get in touch with the author to get a shared understanding of the change.

[jesusbv]

We still need to update the system_token for PAYG systems that do not have it populated but that'd be a different PR