Support server blocks

[cjea]

Description

Reslang does not allow users to define server objects, even though they are generated in both openapi and asyncapi docs. Instead, it creates server objects internally by appending strings to hardcoded hostnames (openapi, asyncapi).

Request

Support server objects in Reslang.

Benefits

• Explicit reslang definitions (i.e no "magic" server names)
• Flexibility in defining different hostnames (e.g api.liveramp.com vs. api-staging.liveramp.com)
• More easily open-sourceable

Proposed syntax

Simplest idea would probably be:

servers {
  "The API server"
  url "api.liveramp.com/my_api"
  scheme "https"

  "LiveRamp Production pubsub instance"
  url "pubsub.liveramp.com"
  port 1883
}

If supporting variables/templating is difficult but desired, that could be addressed in the future and wouldn't block this feature.

[michael-gillett]

However we end up implementing this I would vote that we use host instead of url since url is generally a scheme + host

[liveandrew]

added a fix, merged the PR, and added docs

https://github.com/LiveRamp/reslang/blob/master/docs/server-blocks.md

please re-open if this doesn't suit your needs.