Rename stream destination editor vue component

What does this MR do and why?

This component was used only for HTTP destinations, so we added "http" in the component name to make it explicit.

This also facilitates the upcoming work for this UI:

1. We'll add event type and namespace filters to the other destination categories #524939 (closed)
2. We're updating the APIs, and the Create/Update mutations require too many changes to the existing components, it could become extremely hard to maintain and cleanup afterwards.

Because of the above we'll:

1. Leave the legacy UI be:
   1. stream_http_destination_editor.vue (renamed in this MR) for http legacy destinations
   2. stream_gcp_logging_destination_editor.vue for gcp legacy destinations
   3. stream_amazon_s3_destination_editor.vue for aws legacy destinations
2. In the next MRs: create a consolidated UI to match the consolidated API:

The whole work is under use_consolidated_audit_event_stream_dest_api FF.

MR cadence:

MR	Description
!183848 (merged)	Retrieve streaming destinations from new API
!185411 (merged)	Delete streaming destinations from new API
!186450 (merged) (refactoring)	👈 you're here
!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

References

• Epic: &12339
• Implementation issues: #442447 (closed) / #524939 (closed)
• FF Rollout issue: #523880 (closed)
• FF Cleanup issue: #523881

Screenshots or screen recordings

No UI change

How to set up and validate locally

1. Instance: Your Group > Secure > Audit Events > Streams tab
2. Group: Admin area > Monitoring > Audit Events > Streams tab

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.