implement ability to pass several URIs in different ways

[TarantoolBot]

Product: Tarantool
Since: 2.10.0
Audience/target: Tarantool users
Root document: TBD sections to update

• https://www.tarantool.io/en/doc/latest/reference/configuration/#uri
• https://www.tarantool.io/en/doc/latest/reference/configuration/#cfg-basic-listen
• https://www.tarantool.io/en/doc/latest/reference/configuration/#cfg-replication-replication

SME: @ EvgenyMekhanik

Details

Now there are several ways to pass multiple URIs for box.cfg.listen
and box.cfg.replication:

-- As a string with one or several URIs separated by commas
-- (provides backward compatibility):
box.cfg { listen = "127.0.0.1:3301, /unix.sock, 3302" }
-- As an array which contains string URIs (unambiguous short form):
box.cfg { listen = {"127.0.0.1:3301", "/unix.sock", "3302"} }
-- As an array of tables with 'uri' field
-- (may be extended with more fields in future):
box.cfg {  listen = {
        {uri = "127.0.0.1:3301"},
        {uri = "/unix.sock"},
        {uri = 3302}
    }
}

Requested by @EvgenyMekhanik in tarantool/tarantool@4d10e25

---

While describing the new functional capabilities above, take into account the info from the related doc issue and dev PR

• [2pt] multiple iproto listen sockets #2447
• Multilisten in opensource tarantool#6524

---

Из обсуждения с @ EvgenyMekhanik :

Указаны только эти варианты (синтаксиса), так они являются рекомендованными к использованию и не будут гарантированно изменяться со временем.

По этой фиче были вопросы у продактов. Эти указанные способы гарантированно сохранятся, и их и нужно (и только их!) указывать пользователям.
Возможно стоит сделать акцент на том, что эти способы рекомендованы.

[EvgenyMekhanik]

There are many ways of passing URI with different parameters (same as in URI library tarantool/tarantool@37c3567):

-- Single URI, passed as before
box.cfg({ listen = "/tmp/unix.sock" })
-- Single URI, with query paramters
box.cfg({ listen = "/tmp/unix.sock?q1=v1&q2=v2" })
-- Several URIs with parameters in one string, separated by commas
box.cfg({ listen = "/tmp/unix.sock_1?q=v, /tmp/unix.sock_2?q=v" })
-- Single URI passed in table, with additional parameters, passed
-- in "params" table. This parameters overwrite parameters from
-- URI string (q1 = "v2" in example below).
box.cfg({ listen = {"/tmp/unix.sock?q1=v1", params = {q1 = "v2"}} })
-- Several URIs passed in table with default parameters, passed
-- in "default_params" table, which are used for parameters, which
-- not specified for URI (q3 parameter with "v3" value corresponds
-- to all URIs, and used if there is no such parameter in URI).
box.cfg({ listen = {
        "/tmp/unix.sock_1?q1=v1",
        { uri = "/tmp/unix.sock_2", params = { q2 = "v2" } },
        default_params = { q3 = "v3" }
    }
}) 

Recommended ways for URIs without parameters:

-- As a string with one or several URIs separated by commas
-- (provides backward compatibility):
box.cfg { listen = "127.0.0.1:3301, /unix.sock, 3302" }
-- As an array which contains string URIs (unambiguous short form):
box.cfg { listen = {"127.0.0.1:3301", "/unix.sock", "3302"} }
-- As an array of tables with 'uri' field
-- (may be extended with more fields in future):
box.cfg {  listen = {
        {uri = "127.0.0.1:3301"},
        {uri = "/unix.sock"},
        {uri = 3302}
    }
}

Recommended ways for URIs with parameters:

box.cfg ({  listen = {
        {uri = "127.0.0.1:3301", params = {q1 = "v1"}},
        {uri = "/unix.sock", params = {q2 = "v2"}},
        {uri = 3302, params = {q3 = "v3"}}
    }
})
-- For single URI with parameter is also ok
box.cfg ({ listen = {
    uri = 'localhost:3301',
    params = {
        transport = "ssl",
        ssl_ca_file = "/path_to_ca_file",
        ssl_cert_file = "/path_to_cert_file",
        ssl_key_file = "/path_to_key_file"
    }
}})