GSB API OpenAPI

[pwalski]

Resolves golemfactory/yagna#2415

[nieznanysprawiciel]

@stranger80 Please look at this specification update

[pwalski]

Decided to cancel pending GSB requests on WS close instead of buffering them because I assume this Close might have been caused by this GSB requests, so resending it could create a crash loop.

[stranger80]

Thank you for this precise specification.

Reviewed with some typos, one YAML update and big request to fillthe content of a dedicated GAP article (branch and PR have been added for convenience - golemfactory/golem-architecture#68)

[pwalski]

Method's POST /services response got changed so now it returns Location header with value /{servicesId}
It is an URI relative to /services path.
Response's body field listen.links got replaced with top level servicesId (sitting alongside of listen field).
@prekucki If it is ok then PR golemfactory/yagna#2487 will be merged.
EDIT
It returns field servicesId in a plural form, because it is id for a collection of bound GSB services.
It returns both, a body with servicesId, and Location header because value of this header is not exactly correct - in case of relative form of URI it should use same protocol, which will be happen for DELETE method, but in case of GET it will be ws instead of http. The problem is we are creating WS endpoint using POST which is a bit unusual.