Currently we have a `v1.yaml` file on the `openapi/` folder, with all the methods prepended with `v1`, but that would mean that to bump one method we have to bump all of them by creating a new `v2.yaml` file.
There has to be a better way to be able to handle single-method non-backwards compatible changes.
We might want to define a version rollout strategy too before opening the APIs to any users (ex. doing some kind of preview-stable-deprecated-removed cycle or similar).
This task is to:
* Find a process to add backwards-incompatible changes to the API while having always a backwards-compatible state
* Document the process
* Define a policy on how long each step of that process is going to be, and how we will be notifying the users about the incompatibilities
* If needed, implement a grafana dashboard with the amount of calls to each method (so we know if there's users using each endpoint).