MINOR: Fix Table constraint relationships for SoftDeleted entities.

[IceS2]

Currently Soft Delete and Constraints do not fare well together and on different scenarios it errors.

An example is our E2E MySQL Pipeline where we:

1. Ingest all the Tables
2. Ingest Tables with filters, which prompts to soft delete a couple tables
3. Ingest Tables with other filters, which prompts to restore a couple tables

Some of those tables have different Foreign Key constraints and the process is currently erroring for a couple tables due to two different methods being called:

1. storeEntity (On soft delete)

Here the addConstraintRelationship gets called and searches for the Foreign Key table, which was already soft deleted, raising an exception.

2. updateTableConstraints (On restore entity)

Here the validateTableConstraints gets called and validates the Foreign Key table, which is still soft deleted, raising an exception.

This PR fixes the issues by changing the filter to look also for soft deleted tables both within addConstraintRelationship and validateTableConstraints. I think it makes sense to keep the constraint if there's a soft deleted table in Collate, but if we don't want this or for other weird corner cases we might need to rethink how we are dealing with this flow.

Type of change:

• Bug fix

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[sonarcloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 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 SonarQube Cloud