VLESS inbound: Add "reverses" to set reverse tag by client email

[kastov]

{
  "protocol": "vless",
  "settings": {
    "decryption": "none",
    "flow": "xtls-rprx-vision",
    "clients": [
      {
        "id": "27848739-7e62-4138-9fd3-098a63964b6b",
        "email": "home@example.com"
      },
      {
        "id": "ac04551d-6ebf-4685-86e2-17c12491f7f4",
        "email": "roam@example.com"
      }
    ],
    "reverses": [
      {
        "tag": "reverse-out",
        "email": [
          "home@example.com",
          "roam@example.com"
        ]
      }
    ]
  }
}

[Fangliding]

为什么要这样 会有非常巨大的reverse inbound users么 这是要做什么 或者你有用但是只是加速你自己的非常罕见的用例上的config解析 找不到其他人能用的地方
按此逻辑不是还有 email2flow email2id这些东西

[kastov]

This is just syntax sugar for ease of use. We already have a "flow" at the same level as clients – #5023

In my opinion, flow or reverse (and in general "general" parameters) should have the ability to specify them "globally", outside of clients array.