fix: Update use case terminology and improve date handling in scripts

[Pavan-Microsoft]

Purpose

This pull request standardizes the naming of the telecom use case across the codebase, updates deployment configuration files to match, and improves the logic for adjusting date fields in processed data. The changes ensure consistency in use case references, corrects sample data file selection, and refines date adjustment to only update records when necessary.

Use Case Standardization and Documentation:

• Changed the use case name from 'Contact-center' to 'telecom' in deployment parameter definitions (infra/main.bicep, infra/main.json) and updated sample documentation to refer to "Contact Center (telecom)" for clarity. [1] [2] [3]

Deployment Configuration Improvements:

• Reordered and corrected the dependsOn arrays in infra/main.json to ensure proper resource deployment order and correct DNS zone references. [1] [2] [3]
• Updated the Bicep-generated template hash in infra/main.json to reflect the latest template changes.

Data Processing Logic Fixes:

• Updated the sample data file selection logic in 03_cu_process_data_text.py to use the correct files for the telecom and IT helpdesk use cases, falling back to IT helpdesk as a default.
• Improved the calculation of days_difference when adjusting processed data dates to use only the date part, and ensured updates are only made if days_difference > 0 in both the Python data processing script and the SQL DB service. [1] [2]

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

[github-actions]

🎉 This PR is included in version 3.17.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀