[DSIP-68] Uniformly name process in code as workflow

[SbloodyS]

Search before asking

• I had searched in the DSIP and found no similar DSIP.

Motivation

Uniformly name process in code as workflow for better maintenance

1. First modify the backend code uniformly [Improvement] Uniformly name process in backend code as workflow #16516
2. Then unify the table structure and table fields in backend [Improvement] Unify the table structure and table fields in backend and frontend ui sections #16525
3. Unify the backend controller and frontend ui sections [Improvement] Unify the table structure and table fields in backend and frontend ui sections #16525

Design Detail

Incompatible changes

• Rename tables and fields from process to workflow. eg, from t_ds_process_definition to t_ds_workflow_definition.
• Rename api request/response params from process to workflow. eg, from processDefinitionCode to WorkflowDefinitionCode.

These incompatible changes may affect users of secondary development based on API and Database.

Compatibility, Deprecation, and Migration Plan

No response

Test Plan

Test it with ut, it, e2e, api-test

Code of Conduct

• I agree to follow this project's Code of Conduct

[zhongjiajie]

Maybe we should find out whether another column name should change, related to this issue to avoid too many incompatible upgrades. checking ourselves or collecting from the community

[SbloodyS]

Maybe we should find out whether another column name should change, related to this issue to avoid too many incompatible upgrades. checking ourselves or collecting from the community

Only the upgrade version will be affected.