[Automatic Import][meta] Add support for creating CEL input config

[ebeahan]

Summary

Track work to add chain(s) to create the Common Expression Language (CEL) input config.

Base: [In progress]

The goal of this phase is to support the addition of CEL configs of minimal complexity around paging, chaining API requests and auth.

Requirements:

• [x] Setup new CEL chain
• [x] Add prompt for summarizing the necessary ~paging~ query parameter requirements of the API
• [x] Add prompt for building the CEL program
• [x] Build template for CEL input

Mito

• Add support for running the mito tool necessary for validation
• Add template for dockerfile mock service
• Add template for system tests

Auth:

This is where we'd want to ensure all auth scenarios are supported. In the base phase, we don't add any auth to the program.

Requirements:

• Add any necessary prompts for collecting auth information (basic auth, oauth, api tokens)
• Update CEL builder prompt to allow auth configuration in the program

Validation:

The goal of this would be to expand upon validation. In the base phase, we have basic support for running mito, but now we'd need to focus on how to update the program if any errors occur.

Requirements:

• Add validation prompt(s) to update the program upon finding any errors in mito output

Complexity:

This involves adding support for more complex types of APIs. This includes asynchronous event handling, chaining API requests, and any other common patterns we have.

Requirements:

• Add prompt for identifying any of these common patterns
• Add prompt(s) for each pattern to update the base CEL config generated by the base phase

Input formats:

This is where we'd want to expand our API input beyond only OpenAPI specs, to include PDFs or online doc pages, etc.

Requirements:

• Add support for other formats beyond OpenAPI spec
• Update any necessary prompts to support other input types

[elasticmachine]

Pinging @elastic/security-scalability (Team:Security-Scalability)