Improve workflow between Grok debugger and Ingest Pipelines

[alisonelizabeth]

Problem statement If a user is working with the grok processor within the Ingest Pipelines UI, they have to write grok patterns without any support from the product.

Proposal Add support in Grok Debugger to copy the grok pattern in a format that can be imported into the Ingest Pipelines UI.

Example flow:

1. In Grok debugger, add some sort of visual indicator that allows the user to create a grok processor using the defined grok pattern. Design and copy TBD.

2. Clicking on the button would copy the grok pattern, convert it into a grok processor, and navigate the user to Ingest Pipelines. We can set a default message field, or we could explore allowing the user to define this.

   {
   "processors": [
   {
     "grok": {
       "field": "message",
       "patterns": [
         "%{IP:client} %{WORD:method} %{URIPATHPARAM:request} %{NUMBER:bytes:int} %{NUMBER:duration:double}"
       ]
     }
   }
   ]
   }

3. Ideally, the user is brought directly to the create page in Ingest Pipelines UI with the processors JSON pasted in the modal.

[elasticmachine]

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

[elasticmachine]

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