Support the Readme API ID being set inside the OAS file

[behnam-oneschema]

As we're migrating from manual docs updates to in-repo OAS files, we're having a bunch of job steps which have:

with:
  rdme: openapi docs/category_x.yaml --key=${{ secrets.README_API_KEY }} --id=ID_FOR_CATEGORY_X

From what I see, it looks like there's no way to batch the updates for multiple files in a single command. (Is that correct?)

So, this made me wondering what could be the blockers for being able to have a single command to sync multiple files, and of course the id is a basic one. Now, there are multiple ways to maintain and pass a mapping of file paths/names to ids, but the simples way that comes to mind would be being able to set the readme.com object id of the category directly into the OAS file, similar to the existing extensions, e.g. x-readme-id: ID_FOR_CATEGORY_X.

Having that, supporting syncing of multiple OAS files in a single command seem to be more feasible.

What do y'all think about this?