fix: check existing great expectation suite before adding a new one

[linglp]

Related to: https://sagebionetworks.jira.com/browse/FDS-2155

Problem

Sometimes our GH workflows failed with great expectation suite error:

(1424 durations < 0.005s hidden.  Use -vv to show these durations.)
=========================== short test summary info ============================
FAILED tests/test_validation.py::TestManifestValidation::test_rule_combinations[int-IsNA] - great_expectations.exceptions.exceptions.ExpectationSuiteError: An ExpectationSuite named Manifest_test_suite already exists.
====== 1 failed, 715 passed, 691 warnings, 4 rerun in 1449.84s (0:24:09) =======

I think this problem occurred because the code adds an expectation suite without checking if it exists or not. See the original code below:

self.suite = self.context.add_expectation_suite(
            expectation_suite_name=self.expectation_suite_name,
        )

Link of failed GH action: https://github.com/Sage-Bionetworks/schematic/actions/runs/9893404399/attempts/1

Solution

Check if an expectation suite already exists before adding a new expectation suite. Based on the documentation here, you could use function list_expectation_suite_name to check if an expectation suite has been created. If it does, then we could retrieve the current suite (see documentation here)

[linglp]

This is the same issue as github action workflow run failure here: https://github.com/Sage-Bionetworks/schematic/actions/runs/10014376516/job/27683959671

[GiaJordan]

Just one small comment to address before merge but otherwise looks good!
As an aside at some point we should probably switch to using the GX abbreviation to match how GreatExpectations refers to themselves but that's not pressing at all

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud