Add operationId to openapi spec

[phixMe]

Signed-off-by: Peter Hicks peter@datakin.com

Problem

This adds a property to endpoints in our openapi.yml file to allow clients to be generated with reasonable human-readable function names.

Checklist

• You've signed-off your work
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
• You've versioned your .sql database schema migration according to Flyway's naming convention (if relevant)

[codecov]

Codecov Report

Merging #1978 (7792fd5) into main (47cb6f9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1978   +/-   ##
=========================================
  Coverage     78.23%   78.23%           
  Complexity      955      955           
=========================================
  Files           194      194           
  Lines          5293     5293           
  Branches        420      420           
=========================================
  Hits           4141     4141           
  Misses          706      706           
  Partials        446      446           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[wslulciuc]

Nice! I have some minor naming simplification suggestions for the operation IDs:

• Anything with createOrUpdate* (with some exceptions) I'd use put* (ex: putNamespace). We are planning to apply the same naming conventions to our java / pyclients
• createOrUpdateRun -> createRun, the endpoint is a post and only create runs
• createLineage -> recordLineage

Otherwise, 💯