feat: added kafka events for authentication create and update

[vsrivatsa-juspay]

feat: added kafka events for authentication create and update clickhouse schemas

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR introduces Kafka events for authentication create and update operations. When an authentication record is inserted or updated, an event will now be pushed to the Kafka topic hyperswitch-authentication-events. This feature enables real-time analytics for authentication processes.

Additionally, this PR includes a script to create the necessary ClickHouse schemas to store and query the authentication data.

Changes:
Added Kafka event publishing for authentication create and update operations.
Added script for creating ClickHouse schemas for authentication data.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Pre-requisites
Setting up a 3DS Authenticator and a Payment Processor

1. Modify Development.toml to change the events source:

[events]
source = "kafka"

2. Run the application:

cargo run

3. Start the necessary services using Docker Compose:

docker compose up -d kafka-ui clickhouse-server

4. Create a payment from your server with request_external_three_ds_authentication set to true
5. Initiate the authentication using the generated client_secret:

curl --location 'http:https://localhost:8080/payments/pay_xXr8btC2depRWfVYKmNt/3ds/authentication' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: {{api_key}}' \
--data '{
    "client_secret": "{{client_secret}}",
    "device_channel": "BRW",
    "threeds_method_comp_ind": "Y"
}'

6. Complete the authentication challenge. The status should update to succeeded
   Verification:
   Open ClickHouse UI at http:https://localhost:8123/play.
   Query the authentication table to verify the data:

SELECT * FROM authentications

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[sai-harsha-vardhan]

LGTM