XIA/U4ID: add local U4IDs

Routines for creating, deleting, dumping, and freeing local U4IDs are
added. When a local U4ID is added, a socket is opened on the given
address:port. The socket is marked as an encapsulation socket, which
allows a callback function, u4id_udp_encap_recv, to be registered, which
will be called upon packet delivery on that socket.

Upon receiving an encapsulated XIP packet, u4id_udp_encap_recv
puts the packet on the loopback device so that the packet is
naturally delivered to the xip_rcv function. This passes control
of the packet from the IP stack to the XIA stack.

A new UDP encapsulation type is added to include/uapi/linux/udp.h.

Since local_free_u4id is invoked in an atomic context, the socket
cannot be destroyed. Therefore, a workqueue is used to defer the
socket destruction (and the freeing of the struct fib_xid_u4id_local).
XIA/U4ID: add u4id_deliver and DST I/O functions

If the U4ID to be routed is a local U4ID and it is not a sink, we
have reached the destination of an XIP tunnel. Therefore, the last
node should be advanced and routing may continue.

If the U4ID to be routed is a main U4ID and it is not a sink, we
need to tunnel:

If the packet needs to be written to the network, then an output
function is called. The output functions tunnel the XIP packet by
fetching the IPv4 address and UDP port from the XID and adding
an IP and UDP header to the packet before transmitting it.

If the packet is being received, then an input function is
called. The input functions expand the struct sk_buffer if
necessary, and if the packet came from the network then the
TTL is decreased. The output function is then invoked to write
the packet to the network.
XIA/U4ID: remove requirement to add main table entries

By removing the ability to add main table entries, network administrators
do not have to explicity add the destination of the ephemeral tunnel to
the forwarding table.