[TRIVIAL] Fixed driver OpenAPI /reveal request definition

[mstrug]

Description

OpenAPI driver /reveal request has 3 fields: solutionId, submissionDeadlineLatestBlock, auctionId which is inconsistent with the source code, where /reveal request has only 2 fields: solutionId and auctionId: source.

Changes

/settle and /reveal endpoints have same API definition: Solution, so I've created new API component: SolutionWithDeadline and assigned it to /settle endpoint. From Solution I've removed submissionDeadlineLatestBlock field which now aligns with /reveal endpoint source code.
Renamed driver settle dto module solution.rs to solution_with_deadline.rs and name of the struct Solution to SolutionWithDeadline.

[github-actions]

Reminder: Please consider backward compatibility when modifying the API specification.
If breaking changes are unavoidable, ensure:

• You explicitly pointed out breaking changes.
• You communicate the changes to affected teams.
• You provide proper versioning and migration mechanisms.

---

Caused by:

• crates/driver/openapi.yml

[MartinquaXD]

I think in order to avoid renaming everything every time we add or remove a field we should consider renaming files, top level structs and API references to sth like [reveal_]request and [reveal_]response (same for /solve and /settle)

[mstrug]

I think in order to avoid renaming everything every time we add or remove a field we should consider renaming files, top level structs and API references to sth like [reveal_]request and [reveal_]response (same for /solve and /settle)

Renamed /reveal, /solve and /settle related files and struct names and updated openapi.yml file.

[sunce86]

Tests passing without adjustments in the code show that no breaking changes are introduced.

LGTM

[squadgazzz]

LG

[squadgazzz]

Btw, I suppose, this is not a TRIVIAL but EASY change 🙂