Add versioning for http API

[guillaumerose]

Now that we can remove the binary protocol and the http API is used by both tray, it might be a good idea to introduce versionned API.

The proposition is to copy the current http API under /v1 for instance. The next breaking change could use /v2, and so on.

[cfergeau]

Ideally we'd never break the API, only extend it. However, we already have a plan to rework the current HTTP API, with probably breaking changes, so that will be a good time to also move it under the v1/ umbrella. With our fast release cycle, I don't know how to best approach this though, ideally we'd avoid releasing with /v1 while the API is still being reworked and we cannot commit to it being stable.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cfergeau]

We're still in the process of breaking the API, so this is still valid.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cfergeau]

The HTTP API still isn't finalized/frozen, and I don't think we've added versioning to it yet.

[gbraad]

@anjannath how is this solved?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.