[Quality Management] UI actions to restore default shipped source configurations

[JakovljevicDusan]

What & why

Adds options to unstuck environment from incomplete or damaged source configurations:

1. Make card page editable
2. Action in the card page 'Reset default configuration': Resets this default source configuration shipped with Quality Management, discarding any customizations made to it.
3. Actions in the list page:

• 'Recreate missing default configurations': Recreates any missing default source configurations shipped with Quality Management. Existing default configurations remain unchanged, even if they were customized.
• 'Reset only default configurations': Deletes and recreates the default source configurations shipped with Quality Management, discarding any customizations made to them. Custom source configurations that have been added are preserved.
• 'Reset all configurations': Deletes every source configuration, including custom ones that have been added, and then recreates the defaults shipped with Quality Management.

Linked work

Fixes AB#642625

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ UI}$

The card page's AboutText still states 'It is read-only in most scenarios and intended for advanced configuration.' but this same PR removes the page's Editable = false property, making every field on the page directly editable (and adds a Reset default configuration action). The teaching-tip text now contradicts the page's actual behavior and will mislead users into thinking edits are unusual/discouraged when the page is designed to be edited directly. Update AboutText to reflect that the page is editable and that a Reset action exists to discard customizations to shipped defaults.

_{Agent judgement — not directly backed by a BCQuality knowledge article.}

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.12.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ UI\ &\ Accessibility}$

The PR removes the page-level Editable = false guard from Qlty. Inspect. Source Config. without adding any field-level Editable = false restrictions. Steelman: this may be intended to let advanced users edit mappings inline. But the rest of the diff points the other way: the page now warns that these configurations should not be changed under normal circumstances, shipped defaults get a new reset/undo action with confirmation, and the added tests cover only the reset actions—not direct editing. As written, every record, including shipped defaults, becomes directly editable for fields such as Code, Description, Enabled, From Table No., From Table Filter, To Type, and To Table No., which is a broad write-surface change from the previously read-only UI. If inline editing is intentional, it should be explicitly justified and constrained; otherwise restore the page-level read-only guard or add deliberate field-level editability rules.

_{Agent judgement — not directly backed by a BCQuality knowledge article.}

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.13.4}