[Frontend] Start using new apis instead of existing ones

Problem to solve

Refer Consolidation of tables for streaming audit eve... (&12339) for more details

Adding new streaming destinations and filters takes a lot of time (~3 milestone) and has become cumbersome to maintain across group and instance level. This initiative has consolidated the backend to configuration to simplify and standardise the streaming.

In the rest of this initiative we have created new APIs, but the frontend is still using the old APIs.

Start using new APIs for managing audit event streaming destinations.

Proposal

Update the frontend of both instance and group level streaming components to use the new APIs.

Feature Flag:

• Name: use_consolidated_audit_event_stream_dest_api
• Roll out issue: #523880 (closed)
• Cleanup issue: #523881

APIs can be found here:

1. CRUD APIs for group destinations: #436610 (comment 1862041524)
2. CRUD APIS for instance destinations: #436615 (comment 1862066910)
3. APIs for group event filters: !149691 (merged)
4. APIs for instance event filters: !149704 (merged)

Implementation

MR	Description
!183848 (merged)	Retrieve streaming destinations from new API
!185411 (merged)	Delete streaming destinations from new API
!186450 (merged) (refactoring)	Rename stream destination editor vue component
!186456 (merged) (refactoring)	Add refactored stream destination editor vue component
!186457 (merged)	Add ability to create new stream destinations
!186647 (merged)	Add ability to update stream destinations