fix: Fix to avoid task creation for violent and meaning less prompts when deployment reuse existing AI Foundry Project.

[NirajC-Microsoft]

This pull request introduces changes to improve the handling of existing AI Foundry projects and resources in the infra/main.bicep file. The updates ensure that the code can dynamically use existing resources when specified, reducing redundancy and enhancing flexibility.

Enhancements for handling existing AI Foundry resources:

• Dynamic resource name assignment: Added logic to dynamically assign aiFoundryAiServicesResourceName based on the presence of an existing Foundry project resource ID. If the resource ID exists, the name is derived from it; otherwise, default logic is used.
• Private endpoint configuration updates: Updated private endpoint configurations to use the name from aiFoundryAiServicesConfiguration or the default naming convention, ensuring consistency and adaptability.
• AI Foundry project name assignment: Enhanced the logic for assigning aiFoundryAiProjectName to support existing Foundry projects, deriving the name from the resource ID when applicable. …based on existing and new deployment

Purpose

• ...

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

[Prajwal-Microsoft]

This change is not required as the check is already added in line 701

[github-actions]

🎉 This PR is included in version 2.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀