confirmation-dialog: require button names to comply with ux writing guidelines

[michael-smt]

Prerequisites

• I have read the Contributing Guidelines.
• I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

Feature request

The confirmation dialog defaults to Yes and No buttons, while the UX writing guide says

Avoid using ‘Yes’ and ‘No’ as buttons, but instead use suitable verbs to make the action directly understandable

To ensure the UX writing rule is followed, the confirmBtnName and declineBtnName could be made mandatory.

Use case

Less UX writing review effort required to identify components using the default button names.

Less developer effort to align with UX writing guidelines after the UX writing review.