feat: support set environment variables on flow.dag.yaml

[elliotzh]

Description

This pull request primarily involves changes to the Azure AI ML SDK, with a focus on handling environment variables when loading flow.dag.yaml as a component and modifying test cases.

Environment Variables:

• sdk/ml/azure-ai-ml/assets.json: The tag was updated from python/ml/azure-ai-ml_2ff0425fbf to python/ml/azure-ai-ml_baea630318.
• sdk/ml/azure-ai-ml/azure/ai/ml/_schema/component/flow.py: A dictionary for environment variables was added to _FlowComponentOverridableSchema.
• sdk/ml/azure-ai-ml/azure/ai/ml/entities/_component/flow.py: The handling of environment variables was changed in the __init__ method, with the variables now being read from flow_content and updated with any additional variables [1] [2].

Test Cases:

• sdk/ml/azure-ai-ml/scripts/run_tests.py: The run_simple method was modified to open stdout in text mode instead of binary mode and to not check the output of the subprocess call [1] [2].
• sdk/ml/azure-ai-ml/tests/component/unittests/test_flow_component.py: The test_component_load_from_dag method was updated to include a set of environment variables and a new client_component_hash.
• sdk/ml/azure-ai-ml/tests/pipeline_job/e2etests/test_pipeline_job.py: The test_pipeline_job_with_flow method was modified to assert the validation result message in addition to the pass status.

Test Configurations:

• sdk/ml/azure-ai-ml/tests/test_configs/flows/basic/hello.py: Several changes were made, including the import of VERSION from openai.version, the addition of a get_client function, and modifications to the my_python_tool function to use the new client and check for the AZURE_OPENAI_API_KEY environment variable [1] [2] [3] [4].

Environment Variable Removal:

• sdk/ml/azure-ai-ml/tests/test_configs/flows/runs/basic_run.yml: The AZURE_OPENAI_API_TYPE and AZURE_OPENAI_API_VERSION environment variables were removed.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-ai-ml