KIbana: Issues working with watchers + sensitive data in fields

[frodgim]

Kibana version:
8.6.2

Elasticsearch version:
8.6.2
Server OS version:

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:

Hi Support,
We have experimented with some watcher's execution failures using secret fields.
We have used webhook actions.
When we reopen the watchers we get fields with some special notation. It's just to warn that this field is not possible to read.
i.e : "Authorization": "::es_redacted::"

To here, I think the current behaviour is reasonable due to security risks. The issue here for me is that if you save again the watcher definition, Kibana won't alert you about a possible misconfiguration and it's probably your watcher's action will not work until the next time it's failing, you detect and solve it

Steps to reproduce:

1. Create a watcher, create a webhook action, and fill in the Authorization field with your secret
2. Save the watcher
3. Open again and then save without any changes

Expected behavior:
At least, To be warned about possible misconfiguration

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[alisonelizabeth]

Related to #21010

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)