minor optimization for get_response table, created_at index

[botnumberseven]

If get-response table gets big enough (in my case it's ~2M rows at the moment), then node falls into a restart loop as it timeouts on the query like this:
SELECT id, operation_id AS operationId, keyword, status, message, created_at AS createdAt, updated_at AS updatedAt
FROM get_response AS get_response
WHERE get_response.created_at <= '2024-11-02 15:24:39'
ORDER BY createdAt ASC LIMIT 1000;

adding index on created_at fixes the issue:
ALTER TABLE operationaldb.get_response ADD INDEX idx_created_at (created_at ASC) VISIBLE;