Add Support for Arazzo Specification for the Functional Fuzzer

[BragdonD]

Is your feature request related to a problem? Please describe.

Currently, CATS uses its own file format to define sequences of requests for functional fuzzing. With the emergence of the Arazzo specification from OpenAPI, which provides a standardized way to describe request sequences, it would be beneficial to know if there are plans to support this new specification.

Describe the solution you'd like

I would like to see support for the Arazzo specification within CATS, allowing users to define request sequences using this standard instead of the current custom format. This could either be an alternative input format or a full migration if Arazzo proves to be a better fit.

Describe alternatives you've considered

• Continuing to use the current CATS format.
• Implementing a converter from Arazzo to the current CATS format as a temporary solution.

Additional context

Arazzo is designed specifically for defining sequences of requests in OpenAPI, making it a natural fit for the functional fuzzer. More details about the Arazzo specification can be found here: Azazzo Specification.

[en-milie]

Hi. This is a very good idea. Arazzo Specs seem to be quite young. We'll assess what options there are at the moment for integration.