Cherry-pick #19722 to 7.x: Unroll on unauthorised

[michalpristas]

Cherry-pick of PR #19722 to 7.x branch. Original message:

What does this PR do?

Followup to #19507
This PR detects invalid API token error coming from fleet and after 6 times of retries with backoff in row (should take 5 minutes or so to avoid transient issues). On succ request counter is zeroed.

When unroll is detected (and not coming from fleet) it is not acked but stored in action_store. Removing action store manually will enable agent to ping fleet again. Otherwise it detects it's unrolled on start and prevent talking to fleet

Why is it important?

When API is revoked agent is not notified about this and starts seeing errors. Agent does not know how to handle that and tries to kick fleet periodically

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[blakerouse]

Backport looks good.