Added updatedmode: RSM/SelfUpdate flag in heartbeat (Telemetry helps to determine which/how may vms enrolled into RSM)
Fixing supported feature flag for rsm, when agent does not support GA versioning, we still send as agent supports RSM to CRP. In that case, CRP may send rsm requests and those requests will not be honored by agent. So now don't send RSM supported feature flag if versioning disabled in agent.
For instance, agent is on version N and rsm update attempt failed few times for version N+1 and we send the status to CRP with failed status. Later if we get new request rsm version is same as current version(N), we still sending cached last error msg as rsm status. Fixing that too.
Issue #
PR information
[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made
Description
PR includes minor changes related to RSM
Issue #
PR information
Quality of Code and Contribution Guidelines