ci: Enhance deployment workflows and updated sample data import workflows

[Vamshi-Microsoft]

Purpose

This pull request primarily removes the use of the RESOURCE_TOKEN parameter and related logic from several GitHub Actions workflows, simplifying resource cleanup and deployment processes. Additionally, it improves the PostgreSQL sample data import workflow by automatically discovering the PostgreSQL server in a resource group, eliminating the need for users to manually specify the host name.

Key changes include:

Resource Token Removal and Cleanup Simplification:

• Removed all references to RESOURCE_TOKEN from workflow inputs, environment variables, and job steps in .github/workflows/job-cleanup-deployment.yml, .github/workflows/job-deploy-linux.yml, and .github/workflows/deploy-orchestrator.yml, including the logic for targeted resource cleanup within a resource group. Now, cleanup jobs only handle full resource group deletion. [1] [2] [3] [4] [5] [6] [7] [8]

PostgreSQL Sample Data Import Workflow Improvements:

• The PostgreSQL host name is no longer a required input; instead, the workflow now automatically discovers the first PostgreSQL Flexible Server in the specified resource group and uses it throughout the workflow. This change includes removing related input validation and updating all steps to use the discovered host. [1] [2] [3] [4] [5] [6] [7] [8] [9]

• Added a step to download sample data from Azure Storage, storing it in a temporary directory for use in the data import process.

Resource Group Name Handling:

• Updated .github/workflows/deploy-v2.yml to make the resource_group_name input optional, with an empty string as the default. The workflow now auto-generates a resource group name if not provided, and messaging has been updated accordingly. [1] [2] [3] [4]

Other Minor Cleanups:

• Removed the RESOURCE_TOKEN input from the Windows deployment workflow outputs.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information