[DOCS] Add Dev Tools warning to Security App API subpages or code samples

[peluja1012]

Description

When referring to our API docs, our users frequently falsely assume that our APIs can be used in the Kibana Dev Tools Console. This issue was previously reported and we added a warning to the main Security API docs page, as a result, explaining that the APIs can't be executed from Kibana Dev Tools. However, we need to go one step further and find more ways to communicate this to users. Maybe we need to add a warning or information icon above the code samples. Or maybe we need to add the warning to API docs subpages as well. Open to suggestions!

https://www.elastic.co/guide/en/security/current/security-apis.html

[jmikell821]

Hi @peluja1012 thanks for raising this issue. We can start by adding a warning to the API subdoc pages, then we'll see if we need to add this warning elsewhere. We'll be sure to add this warning if we create new API code samples.

[nastasha-solomon]

I inserted the note into all API docs except for the following because they weren’t referenced in this top-level topic.

• Actions API (for pushing cases to external systems)
• Create connector
• Update connector
• Create or update an external incident

@peluja1012, if the Kibana Dev Tools Console doesn't support these APIs either, I can insert the note into these topics as well.

[nastasha-solomon]

@peluja1012, I verified with @XavierM that the Kibana Dev Console does not support the Action APIs that push cases to external cases. Updating those last four topics now and will push the changes to the PR.