Bug: include FOR ROLE in ALTER DEFAULT PRIVILEGES DDL has broken the Supabase migrations

[silentworks]

It would be good if there was a way to turn off including FOR ROLE inside of the generated schema. This has caused the schema to break when working with Supabase. I was using version 1.6.0 and then started working on my other computer with a fresh install which was the latest 1.7.2 version at the time and noticed my project was having issues running the migrations. It was generating diffs with FOR ROLE in them when I call plan and then when I tried to apply them I would get an error about not being able to alter default privileges. Supabase didn't like the fact that the postgres role was trying to set default privileges for the supabase_admin role.

I have since reverted to 1.6.0 and all is working properly again.

This issue was introduced in this PR: #236

[tianzhou]

Please provide a detailed script. I will make sure that we address this properly.