Add SO_INCOMING_CPU support to net.sock_option_flag_in

[masaori335]

Address #5165.

Add a option (128) for SO_INCOMING_CPU to the proxy.config.net.sock_option_flag_in.

Background

There was a bug with SO_REUSEPORT since v4.6. But it's fixed by v6.2 and some distros backported it.
Now we can use SO_INCOMING_CPU, SO_REUSEPORT and CPU Affinity 4 for perfect locality.

torvalds/linux@b261eda

Ref.

    SO_INCOMING_CPU (gettable since Linux 3.19, settable since Linux 4.4)

          Sets or gets the CPU affinity of a socket.  Expects an
          integer flag.

              int cpu = 1;
              setsockopt(fd, SOL_SOCKET, SO_INCOMING_CPU, &cpu,
                         sizeof(cpu));

          Because all of the packets for a single stream (i.e., all
          packets for the same 4-tuple) arrive on the single RX
          queue that is associated with a particular CPU, the
          typical use case is to employ one listening process per RX
          queue, with the incoming flow being handled by a listener
          on the same CPU that is handling the RX queue.  This
          provides optimal NUMA behavior and keeps CPU caches hot.

https://www.man7.org/linux/man-pages/man7/socket.7.html

[masaori335]

The hwloc_obj::os_index looks "OS-provided physical index number" and it's working with exec_thread.affinity: 4 as expected. However, hwloc has any better API?
https://github.com/open-mpi/hwloc/blob/63a8288d31a1baf67a909466aba9a022c78ca7b1/include/hwloc.h#L491

[masaori335]

@cmcfarlen I'd request to 10.0.x backport. But, this is a new feature, so we can wait for 10.1.x, if you want.

[cmcfarlen]

Cherry-picked to v10.0.x