Before reporting an issue

• I have searched existing issues
• I have reproduced the issue with the latest nightly release

Area

user-profile

Describe the bug

When creating or updating an attribute, setting the Required when setting to Always still persists the scopes from the Scopes are requested option.

The Always and Scopes are requested are mutually exclusive.

Version

22.0.4

Expected behavior

The Admin UI should work as follows:

• If the Enabled when setting is set to Always, the selector JSON field of the attribute configuration should not be set at all.
• If the Required when setting is set to Always, the required.scopes JSON field of the attribute configuration should not be set at all.

Actual behavior

The client scopes are always set when enabling or marking a feature as required even though the Always option is set.

How to Reproduce?

See #20852 (comment).

Anything else?

Created from #20852 (comment).