[Python] Keep deprecated fields in Python code

[kanterov]

Changes

Python code generation doesn't remove deprecated fields anymore unless they were deprecated during Private Preview. A few fields are manually excluded because they have been deprecated for many years and have never functioned.

Remove ForceNotDeprecated annotation because it isn't needed anymore.

Why

During updates, removing deprecated fields immediately can be surprising because there is no prior notice. There are also bundles that rely on the usage of deprecated fields.

Tests

By looking at diffs in the generated code

[denik]

qq - is there a limitation in this schema that prevents use of boolean here? (I'm not familiar with this code, so just asking).

[kanterov]

@denik for booleans, we will have to use a boolean pointer to have 3 states: nil (unset), false, and true. I think enums are cleaner for that.

[eng-dev-ecosystem-bot]

Run: 17323263361

	Env	✅​pass	🙈​skip
✅​	aws linux	308	504
✅​	aws windows	309	503
✅​	aws-ucws linux	421	401
✅​	aws-ucws windows	422	400
✅​	azure linux	308	503
✅​	azure windows	309	502
✅​	azure-ucws linux	421	400
✅​	azure-ucws windows	422	399
✅​	gcp linux	307	505
✅​	gcp windows	308	504

[kanterov]

@pietern @denik updated the code following our discussion. If we exclude deprecated private fields, there are only a few examples manually excluded that shouldn't make it into SDK v1.

[pietern]

Do you have examples of these?

They should rather be removed from the spec entirely.

[kanterov]

Yes, there are many of them. Should we remove them from the JSON schema altogether? For example, in jobs.TriggerSettings:

                    "table": {
                      "description": "Old table trigger settings name. Deprecated in favor of `table_update`.",
                      "$ref": "#/$defs/github.com/databricks/databricks-sdk-go/service/jobs.TableUpdateTriggerConfiguration",
                      "x-databricks-preview": "PRIVATE",
                      "deprecationMessage": "This field is deprecated",
                      "doNotSuggest": true,
                      "deprecated": true
                    },
                    "table_update": {
                      "$ref": "#/$defs/github.com/databricks/databricks-sdk-go/service/jobs.TableUpdateTriggerConfiguration",
                      "x-databricks-preview": "PRIVATE",
                      "doNotSuggest": true
                    }

I think following the principle, we should remove them from SDK v1