Update integrations and automation user interface to use new dedicated endpoints

[lukeheath]

Goal

As an Engineer, I want to manage integrations and automations using REST endpoints so that I can interact with the API using established patterns.

Requirements

1. Stop relying on global configuration object for integrations and automations.
2. Instead, use new REST endpoints created as part of #8188

Related issues

• 8188

Tasks

Specced by @RachelElysia assuming we are making a breaking change

GET, POST, PATCH, and DELETE endpoints for /integrations and /automations

1 Update frontend/interfaces/config.ts

• [ ] Remove webhook_settings: IWebhookSettings; from config object
• [ ] Remove integrations: IIntegrations; from config object

2 Create frontend/interfaces/automations.ts and update frontend/interfaces/integrations.ts

• [ ] Create IAutomations interface to use current IWebhooks
• [ ] Update IIntegration and related interfaces to match the new API

3 Update frontend/interfaces/team.ts

• [ ] Update ITeamAutomationsConfig to use the appropriate new interfaces

4 Create frontend/services/entities/integration.ts

• [ ] loadAll
• [ ] update
• [ ] delete
• [ ] Allows for team integration

5 Create frontend/services/entities/automations.ts

host status webhook

• [ ] load
• [ ] update (enable/disable, percentage, destination url, days count)
• [ ] delete failing policies webhook
• [ ] load
• [ ] update (enable/disable, destination url, policy ids, host batch size)
• [ ] delete software vulnerabilities webhook
• [ ] load
• [ ] update (enable/disable, destination url, host batch size)
• [ ] delete

4 IntegrationsPage.tsx

• [ ] Update configAPI.loadAll() to integrationAPI.loadAll()
• [ ] Update combineJiraAndZendesk function to new API usage (should simplify combining the two with the new API endpoints!)

5 Software page ManageAutomationsModal.tsx

• [ ] Update to use both /integrations and /automations for create/update/delete a vulnerable software webhook/integration
• [ ] This should simplify the combination of integrations with the new API endpoints!

6 Policy page ManageAutomationsModal.tsx

• [ ] Update to use both /integrations and /automations for create/update/delete a failing policy webhook/integration
• [ ] This should simplify the combination of integrations with the new API endpoints!

7 Update settings > organization > host-status-webhook HostStatusWebhook.tsx

• [ ] Remove get/update of appConfig
• [ ] Replace with get/update /automations endpoint
• [ ] host status webhook
• [ ] load
• [ ] update (enable/disable, percentage, destination url, days count)
• [ ] delete

8 Ensure any remaining /config endpoint has all /integrations and /automations stuffz removed

• [ ] QA to make sure things related to /config work correctly now that we removed webhook_settings and integrations from the endpoint

9 Update e2e tests

• [ ] Update all integration mocks through /config and create mocks through /automations (should simplify the mocks with the new API endpoints!)

[lukeheath]

@RachelElysia I am assigning you this ticket to complete the implementation specs. The backend portion will go into the next release, then we'll bring this ticket into the following release after the backend is implemented.

[lukeheath]

Moving issue off roadmap board because v5 has been deferred.