fix(tests): remove overly strict updatedAssets assertions from delete/purge tests

[cmgrote]

Summary

• The Atlan backend started returning cascading side-effected assets in the UPDATE bucket of delete responses around April 10, 2026 (e.g. parent glossary appears in updatedAssets when a child term is soft-deleted)
• Removed assertTrue(response.getUpdatedAssets().isEmpty()) and assertEquals(response.getUpdatedAssets().size(), 0) assertions from all delete/purge test methods across 20 test files
• Retained these assertions in create-operation methods where they remain valid (GlossaryTest, ConnectionTest, PersonaTest, PurposeTest, AtlanLiveTest, ModelTest)
• The meaningful delete-success signals — getDeletedAssets().size(), asset GUID/qualifiedName, status DELETED, and deleteHandler — are all preserved

Fixes: BLDX-1041

Test plan

• Integration tests should now pass for all delete/purge methods that were previously failing with AssertionError: expected [true] but found [false]
• Create-operation assertions remain unchanged and unaffected

🤖 Generated with Claude Code