Configurable Bulk Copy Timeout Setting for SQL

Summary:
Introduce a configurable Bulk Copy Timeout setting for SQL Server exports in Integration Pro, similar to the existing Oracle configuration. This setting will allow administrators to adjust the client‑side timeout for bulk copy operations so large data exports can complete reliably without premature failures.

Problem Statement:
Currently, Integration Pro uses a bulk copy mechanism when exporting data to SQL Server to improve performance by sending data in large batches rather than row by row. For customers exporting high volumes of data, these operations can exceed SQL Server’s default client‑side bulk copy timeout of 30 seconds. Because this timeout is enforced on the client, not in the database itself, it cannot be tuned via SQL Server configuration. As a result, long‑running exports may fail even when the database can handle the workload, forcing users to break jobs into smaller runs or retry repeatedly.

Proposed Solution:
Add a configurable Bulk Copy Timeout setting for SQL Server exports in Integration Pro, mirroring the flexibility already available for Oracle.
Allow administrators to specify the timeout value (in seconds) per connection or integration profile so it can be tuned based on data volume, environment performance, and SLAs.
Ensure the new setting is clearly exposed in the Integration Pro UI and/or configuration files, with a sensible default (e.g., 30 seconds) and documented maximum value.
Apply the configured timeout consistently across all SQL Server bulk export operations, and provide informative error messages when a timeout is reached (including which setting value was in effect).
Maintain backward compatibility by defaulting to the current behavior for existing configurations where the setting is not explicitly changed.

Benefits:
Reduces failed export jobs for large data sets by allowing timeouts to be tailored to real‑world performance.
Improves reliability and predictability of Integration Pro SQL Server exports, especially in high‑volume or slower network environments.
Decreases manual effort required to split or rerun exports due to arbitrary timeout limits.
Aligns SQL Server behavior with existing Oracle configuration capabilities, creating a more consistent admin experience across database types.