FIX: reverted deprecated fields on testSuite

[sushi30]

Problem

Following #19221, migrations fail because MigrationUtils rely on objects which use the old schema that contains deprecated fields.

Example Failure

Failed to db migration due to 
org.openmetadata.service.exception.UnhandledServerException: An exception with message [Failed to process JSON ] was thrown while processing request.
	at org.openmetadata.service.util.JsonUtils.readValue(JsonUtils.java:186)
	at org.openmetadata.service.migration.utils.v157.MigrationUtil.migrateTableDiffParams(MigrationUtil.java:36)
	at org.openmetadata.service.migration.postgres.v157.Migration.runDataMigration(Migration.java:18)
...
aused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "executable" (class org.openmetadata.schema.tests.TestSuite), not marked as ignorable (34 known properties: "domain", "testCaseResultSummary", "votes", "lifeCycle", "name", "testConnectionResult", "updatedAt", "serviceType", "pipelines", "followers", "version", "deleted", "basicEntityReference", "id", "fullyQualifiedName", "connection", "owners", "tests", "summary", "href", "changeDescription", "displayName", "basic", "style", "updatedBy", "certification", "description", "extension", "experts", "reviewers", "tags", "inherited", "dataProducts", "children"])
 at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 650] (through reference chain: org.openmetadata.schema.tests.TestCase["testSuites"]->java.util.ArrayList[0]->org.openmetadata.schema.tests.TestSuite["executable"])

Proposed Solution

Keep the deprecated along with a useful description regarding the field that replaces it as well as adding the @Deprecated annotation for the field in the created java object. The only context where these deprecated fields should be used is in migrations prior to the version where it was deprecated.

Example deprecated field

/**
 * DEPRECATED in 1.6.2: Use 'basic'
 * 
 */
@JsonProperty("executable")
@Deprecated
public Boolean getExecutable() {
    return executable;
}

Future work

These fields will might be included in some contexts where the json documents are consumed fully (API responses. elasticsearch, etc). Need to make sure they are cleaned up by default in these places.

Describe your changes:

Fixes

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]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	64.59% (40790/63157)	40.81% (16365/40102)	43.97% (4951/11260)

[sonarqubecloud]

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

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

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

[github-actions]

Changes have been cherry-picked to the 1.6.2 branch.