SSDT for synapse dw project Maintain user permission after table change published

Nobody has claimed this yet.

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
Please describe the desired behavior.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Description:
SSDT for synapse dw project Maintain user permission after table change published
Customer Scenario:

Keep user permission after table column changes

cx is using github + ssdt to source control DEV, UAT, PROD envrionments, if they change a column type etc will result in table rebuild(build new table, import data from old table to new table, drop old table, rename new table), cx did not maintain user permission in source control as they wish to maintain different permission in different environment, thus user permission will be lost after table rebuild.

The issue does not name an implementation file, test, or entry point. Start by clarifying how SSDT for Synapse data warehouse projects represents permissions and table rebuilds, including the expected behavior across environments. Done means publishing a table column change preserves the intended user permissions.

Written by the indexing model from the issue text.