chore: do not store merged openapi spec inside customer repository

[ThomasRooney]

No description provided.

[simplesagar]

wouldn't we want to store the merged file in repo?

[ThomasRooney]

wouldn't we want to store the merged file in repo?

We don't right now -- we might want to expose it as a configuration option but as it is a transient file it doesn't really make sense.

The main reason why not to today, is that when we merge together openapi specs we are re-rendering it with LibOpenAPI, which causes formatting flux. Right now, libopenapi renders non-deterministically when we merge together multiple files, due to the current simplicity of the sorting mechanism (it only renders deterministically when it is generated from a source file, rather than several in-memory structures).

This means that a "generation" diff is unnecessarily hard to review, as things like paths are effectively randomly sorted every time in the openapi_merged file.