Add SCRAM-SHA-256 support to postgres states

[OrangeDog]

What does this PR do?

Adds SCRAM-SHA-256 support to postgres states.

What issues does this PR fix or reference?

Fixes: #51217

Previous Behavior

See referenced issue. Only plaintext and MD5 passwords supported.

New Behavior

If encrypted=scram-sha-256 is passed to the postgres_user.present or postgres_group.present states then the SCRAM-SHA-256 algorithm is used.

Other minor issues fixed:

• If encryption is disabled by default, it cannot be enabled
• Return says role was created when it was updated
• Errors ignored from postgres_group.absent
• Incorrect handling of group membership changes in postgres_group.present

Merge requirements satisfied?

[NOTICE] Bug fixes or features added to Salt require tests.

• Docs
• Changelog - https://docs.saltstack.com/en/master/topics/development/changelog.html
• Tests written/updated

[OrangeDog]

I did a manual integration test. If it's possible for someone to add something with some postgres Docker images that would be awesome.

[sagetherage]

Since this is a new feature and is pretty cool, can we get it added to Release Notes?

[OrangeDog]

Since this is a new feature and is pretty cool, can we get it added to Release Notes?

(How) do I do that?

[garethgreenaway]

@OrangeDog You'll want to add some information to the release notes for 3003, which can be found here: salt/doc/topics/releases/3003.rst within the code base.

[garethgreenaway]

@OrangeDog Apologies for the delay in getting to this. Since we missed the 3003 release, would you be able to update the PR to have the note in release notes for the Aluminum release? Thanks!

[OrangeDog]

But Aluminium is 3003...

[sagetherage]

I think Gareth might be confused in that comment. @OrangeDog there was a test that cancelled out, but I have updated this PR with the master branch and that will re-run those and we can look again at getting this merged soon for Aluminium or 3003 release.

@OrangeDog Apologies for the delay in getting to this. Since we missed the 3003 release, would you be able to update the PR to have the note in release notes for the Aluminum release? Thanks!

[sagetherage]

@Ch3LL this is looking close

[garethgreenaway]

Looks good. @Ch3LL when you get a chance this one is ready to go.

[Ch3LL]

same as here

[OrangeDog]

It looks like adding the lines back to filename_map.yml has resulted in The command line is too long on Windows.
Nothing can be done about that here - the whole test running system will need a re-work unless there's an easy way to disable the limit.

[s0undt3ch]

It looks like adding the lines back to filename_map.yml has resulted in The command line is too long on Windows.
Nothing can be done about that here - the whole test running system will need a re-work unless there's an easy way to disable the limit.

That is correct and a limitation on Windows which should be addressed.

Right now, I've triggered the full test suite run for both Windows which bypasses this problem

[dwoz]

It looks like adding the lines back to filename_map.yml has resulted in The command line is too long on Windows.
Nothing can be done about that here - the whole test running system will need a re-work unless there's an easy way to disable the limit.

That is correct and a limitation on Windows which should be addressed.

Right now, I've triggered the full test suite run for both Windows which bypasses this problem

I'm going to merge this for Aluminum, @OrangeDog Please create a ticket for the issue which needs to be addressed on windows.