GitLab

- Remove leading slash from v2 WAF API route paths
- Ensure consistent route path formatting

- Integrate Elasticsearch client for querying WAF attack logs
- Add new API endpoints for listing attack logs and WAF rules
- Implement pagination and filtering for attack log retrieval
- Support language-based rule category display
- Update service and controller layers to support new functionality

- Modify WAF route to use empty string for root path
- Remove commented-out route for gateway endpoint
- Simplify route configuration in `SetWafRouter`

- Remove path parameters from route configuration
- Align with previous changes to use query-based parameter retrieval

- Update WAF router configuration to use POST method for enabling multiple listeners
- Maintain consistency with other WAF-related API endpoint HTTP methods

- Introduced new API endpoint and service method to enable/disable WAF for multiple listeners
- Updated router, controller, and service to support bulk listener WAF operations
- Added new request type `EnableListenerWafsReq` to handle multiple listener configurations
- Implemented logic to add or remove WAF configurations for specific listeners based on input

- Modified SQL migration to add 'hosts' column to gateway_listeners table
- Updated model, service, and controller to support hosts in gateway listener operations
- Added new GetWafGatewayInfo method to retrieve WAF gateway information
- Refactored WAF service methods to handle hosts and improve flexibility