[ResponseOps][Cases] Remove configuration's deleted custom field from template's custom fields via API

[js-jankisalvi]

Summary

Parent issue: #181309

This PR takes care of below scenario:
When user deletes custom fields via API, those custom fields need to be removed from templates as well.

Flaky test runner

Testing

• create a custom field in settings page
• create a template with that custom field in settings page
• Get configuration via postman for same owner, should have customFields and templates attribute similar to this:

[
    {
        "customFields": [
            {
                  "key": "new_custom_field_key_2",
                  "type": "toggle",
                  "label": "My toggle custom field",
                  "required": "false",
            }
         ],
        "templates": [
            {
                "key": "template_key_1",
                "name": "Template with CF1",
                "caseFields": {
                     "customFields": [
                        {
                            "key": "new_custom_field_key_2",
                            "type": "toggle",
                            "value": false
                        }
                    ]
                },
            
            },
        ],
        "version": ${config_version}
        "id": ${config_id}
    }
]

• run the patch request via postman to delete the custom field, e.g:

path: https://localhost:5601/api/cases/configure/config_id

body: 
{
        "customFields": [],
        "templates": [
            {
                "key": "new_template_key_1",
                "name": "New template",
                "caseFields": {
                    "customFields": [
                        {
                            "key": "new_custom_field_key_2",
                            "type": "toggle",
                            "value": true
                        }
                    ]
                }
            }
        ],
    "version": "test-version"
}

• validate that custom field is removed from templates as well

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[doakalexi]

Tested locally and works as expected, LGTM!

[adcoelho]

LGTM left a minimal comment 👍

[js-jankisalvi]

@elasticmachine merge upstream

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6376

[✅] x-pack/test/cases_api_integration/security_and_spaces/config_basic.ts: 25/25 tests passed.
[✅] x-pack/test/cases_api_integration/security_and_spaces/config_trial.ts: 25/25 tests passed.

see run history

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6377

[✅] x-pack/test/cases_api_integration/security_and_spaces/config_basic.ts: 25/25 tests passed.
[✅] x-pack/test/cases_api_integration/security_and_spaces/config_trial.ts: 25/25 tests passed.

see run history

[cnasikas]

LGTM!

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 73c34ee
• Interpreting CI Failures

Failed CI Steps

• Post-Build

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [7e92302]

History

• 💔 Build #217375 failed 21b2b0d
• 💔 Build #217156 failed 2aa6190
• 💔 Build #217115 failed fc94724

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @js-jankisalvi