release-24.1: ui: alter role events render correctly

[blathers-crl]

Backport 1/1 commits from #126354 on behalf of @dhartunian.

/cc @cockroachdb/release

---

Previously, ALTER ROLE events without role options would render with an "undefined" option in the event log on the DB Console. This change amends the rendering logic to correctly render events without any options.

Resolves #124871
Epic: None

Release note (bug fix,ui change): ALTER ROLE events in the DB Console event log now render correctly when the event does not contain any role options.

---

Release justification:

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Backports should only be created for serious
  issues or test-only changes.
• Backports should not break backwards-compatibility.
• Backports should change as little code as possible.
• Backports should not change on-disk formats or node communication protocols.
• Backports should not add new functionality (except as defined
  here).
• Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
• All backports must be reviewed by the owning areas TL and one additional
  TL. For more information as to how that review should be conducted, please consult the backport
  policy.

If your backport adds new functionality, please ensure that the following additional criteria are satisfied:

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
• Your backport must be accompanied by a post to the appropriate Slack
  channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

[cockroach-teamcity]

This change is 

[rafiss]

Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @blathers-crl[bot], @kyle-a-wong, and @nkodali)

---

pkg/ui/workspaces/db-console/src/util/events.ts line 184 at r1 (raw file):

        return `Role Altered: User ${info.User} altered role ${info.RoleName} with options ${info.Options}`;
      } else {
        return `Role Altered: User ${info.User} altered role ${info.RoleName}`;

if options isn't present, then the event will be defined as:

cockroach/pkg/sql/alter_role.go

Lines 503 to 506 in c4065c0

	&eventpb.AlterRole{
	RoleName: roleName.Normalized(),
	SetInfo: []string{"DEFAULTSETTINGS"},
	})

it might be worth checking that the SetInfo field is populated, but that would just be a sanity check since that field always will contain a constant string (DEFAULTSETTINGS).

i do think it would be useful for this message to say something more specific, like User %{info.User} altered default session variables for role ${info.RoleName}`. this backport lgtm, but if you agree, that change can be made in a separate PR.

[dhartunian]

ack @rafiss I'll put up a separate PR to iterate on this a second time. Thanks for the advice.

Tracking in #127182