added restart upgrade action

[juliaElastic]

Summary

Ready to review, tests are WIP

Resolves #135539

For agents in Updating state, adding a Restart upgrade action, which uses the force flag on the API to bypass the updating check. For single agent, the action is only added if the agent has started upgrade for more than 2 hours (see discussion in issue)
For bulk selection, the action appears if all selected agents are in updating state.

To verify:

• Start local es, kibana, fleet server (can be docker)
• Enroll agents with horde
• update agent docs with the queries below to simulate stuck in updating for more than 2 hours (modify the query to target specific agents)
• bulk select agents and check that Restart upgrade action is visible, and it triggers another upgrade with force flag only on the agents stuck in updating
  • when calling the bulk_upgrade API, the UI adds the updating condition to the query / or includes only those agent ids that are stuck in updating, depending on query or manual selection

curl -sk -XPOST --user elastic:changeme -H 'content-type:application/json' \
http://localhost:9200/_security/role/fleet_superuser -d '
   {
      "indices": [
            {
               "names": [".fleet*",".kibana*"],
               "privileges": ["all"],
               "allow_restricted_indices": true
            }
      ]
   }'

curl -sk -XPOST --user elastic:changeme -H 'content-type:application/json' \
http://localhost:9200/_security/user/fleet_superuser -d '
   {
      "password": "password",
      "roles": ["superuser", "fleet_superuser"]
   }'

    curl -sk -XPOST --user fleet_superuser:password -H 'content-type:application/json' \
    -H'x-elastic-product-origin:fleet' \
    http://localhost:9200/.fleet-agents/_update_by_query -d '
    {
       "script": {
         "source": "ctx._source.upgrade_started_at = \"2023-09-13T11:26:23Z\"",
         "lang": "painless"
       },
       "query": {
         "exists": {
           "field": "tags"
         }
       }
     }'

Agent details action:

Agent list, bulk action:

Agent list, single agent action:

Agent details callout:

Select all agents on first page, restart upgrade modal shows only those that are stuck in upgrading:

Select all agents on all pages, restart upgrade modal shows only those that are stuck upgrading, with an extra api call to get the count:

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 8d97562

Failed CI Steps

• FTR Configs #18

Test Failures

• [job] [logs] FTR Configs #18 / serverless observability UI Cases list "before all" hook in "Cases list"

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	1.2MB	1.2MB	+4.1KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	142.8KB	143.0KB	+261.0B

History

• 💔 Build #159174 failed fb243ed
• 💔 Build #159122 failed da21e50
• 💔 Build #158987 failed 42f955e
• 💔 Build #158749 failed 0cdcfeb
• 💔 Build #158659 failed b019ef7

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @juliaElastic

[nchaulet]

Code LGTM 🚀