Updated ConfirmAsync so it uses new DefaultUseYesNo property as the ConfirmConfig overload does - #804

Description of Change

In my last PR I sadly forgot to also let the ConfirmAsync overload without ConfirmConfig parameter make use of the new DefaultUseYesNo property. This PR changes that.

Issues Resolved

Fixes that using ConfirmAsync with and without ConfirmConfig parameter will result in different button texts when using DefaultUseYesNo = true and not setting OkText and/or CancelText.

API Changes

None

Platforms Affected

• All

Behavioral Changes

ConfirmAsync with and without ConfirmConfig parameter will now result in the same output (as originally intended), when using DefaultUseYesNo = true and not providing OkText and/or CancelText.

PR Checklist

• Rebased on top of the target branch at time of PR
• Changes adhere to coding standard