fix(tests): Use the shared session fixtures in the new integ tests

Both new integ tests defined local sagemaker_session and pipeline_session
fixtures returning a bare Session() / PipelineSession(), shadowing the
shared ones in tests/integ/conftest.py. CI runs the integ suite with
AWS_DEFAULT_REGION unset, so a bare session has no region and both tests
error at setup with "Must setup local AWS configuration with a region
supported by SageMaker".

The local role fixture went too, since the shared conftest provides one. The
shared fixtures build on a boto3.Session carrying an explicit region, which
is exactly what was missing.

Found on the v2 equivalent of these tests, where CI reported it; the same
shadowing was present here and would have failed the same way once these
tests ran.

Testing: both integ tests re-run against the service using the shared
fixtures -- lineage in 15.62s with AWS_DEFAULT_REGION unset, and the chained
EndpointConfig -> Endpoint -> InferenceComponent pipeline in 413.44s -- with
no resources left behind. 327 workflow unit tests still pass.
---
X-AI-Prompt: did you read the comment on the pr?
X-AI-Tool: kiro-cli

Author: Rishabh Devnani

sagemaker-mlops/tests/integ/workflow/test_deployment_steps.py

@@ -31,8 +31,6 @@
 import pytest
 
 from sagemaker.core import image_uris
-from sagemaker.core.helper.session_helper import Session, get_execution_role
-from sagemaker.core.workflow.pipeline_context import PipelineSession
 from sagemaker.mlops.workflow.endpoint_step import EndpointConfigStep, EndpointStep
 from sagemaker.mlops.workflow.inference_component_step import InferenceComponentStep
 from sagemaker.mlops.workflow.pipeline import Pipeline
@@ -42,19 +40,10 @@
 POLL_SECONDS = 30
 
 
-@pytest.fixture
-def sagemaker_session():
-    return Session()
-
-
-@pytest.fixture
-def pipeline_session():
-    return PipelineSession()
-
-
-@pytest.fixture
-def role():
-    return get_execution_role()
+# sagemaker_session, pipeline_session and role come from tests/integ/conftest.py.
+# They build their sessions on a boto3.Session carrying an explicit region, which a
+# bare Session() would not have: CI runs the integ suite with AWS_DEFAULT_REGION
+# unset.
 
 
 def test_deployment_steps_execute_end_to_end(sagemaker_session, pipeline_session, role):

sagemaker-mlops/tests/integ/workflow/test_lineage_step.py

@@ -36,11 +36,9 @@
 
 import pytest
 
-from sagemaker.core.helper.session_helper import Session, get_execution_role
 from sagemaker.core.lineage.action import Action
 from sagemaker.core.lineage.artifact import Artifact
 from sagemaker.core.lineage.context import Context
-from sagemaker.core.workflow.pipeline_context import PipelineSession
 from sagemaker.mlops.workflow.lineage_step import (
     LineageAssociation,
     LineageEntityReference,
@@ -49,19 +47,10 @@
 from sagemaker.mlops.workflow.pipeline import Pipeline
 
 
-@pytest.fixture
-def sagemaker_session():
-    return Session()
-
-
-@pytest.fixture
-def pipeline_session():
-    return PipelineSession()
-
-
-@pytest.fixture
-def role():
-    return get_execution_role()
+# sagemaker_session, pipeline_session and role come from tests/integ/conftest.py.
+# They build their sessions on a boto3.Session carrying an explicit region, which a
+# bare Session() would not have: CI runs the integ suite with AWS_DEFAULT_REGION
+# unset.
 
 
 def test_lineage_step_execute_end_to_end(sagemaker_session, pipeline_session, role):