Add testdrive self-managed password authentication tests on upgrade

[SangJunBak]

Add self-managed password authentication tests

Add tests to test self managed password auth for past patch releases upgrading to the latest self managed patch release

Motivation

Followup for incident 697

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[SangJunBak]

@def- SQLLogictests failed bc. enabled_password_auth creates a code path that handles role creation differently. Not sure if I should adjust these tests or disable password auth for them. I think role.slt and role_create.slt can just be updated since all it tests is that the LOGIN, SUPERUSER syntax is invalid for cloud. However pg_catalog_user.slt explictly tests against a code path for email domains.