Update supautils.conf.j2 | removed users permission to update log_sta…

[TheOtherBrian1]

What kind of change does this PR introduce?

Modifies supautils.

What is the current behavior?

Users can change log_statements

What is the new behavior?

Revokes users' permission to change the log_statements

Additional context

log_statements should be set to ddl. It was assumed that users would expand it to ddl, write,..., but not remove the default setting. A Team Customer's instance had a setting of none. As a result, uncovering why objects have been dropped has become nearly impossible.

Ensuring DDL commands are logged is essential for both users and Support for uncovering hacks, rogue AI queries, and internal vandalism between project owners.

Add any other context or screenshots.

[soedirgo]

This is a difficult move to justify because it's a breaking change and it prevents higher levels of logging (which may in turn result in more tickets). Looking into the ticket to get more details

[steve-chavez]

The ideal solution would be to disable the none value instead. supautils has a feature that disable values for GUC placeholders (ref1 and ref2), but this won't work for already defined GUCs IINM. We would need to see if that can be made to work somehow.

[soedirgo]

The ideal solution would be to disable the none value instead

It'd still be a breaking change.

Root cause has been addressed in the linked ticket, so closing this.