Add TCP and Unix Socket permissions

[FabienGhd]

Hi,

This PR fixes issue #130.
This blog also raises the same caveat when using Udica with the kata-monitor daemonset in Kata Containers, stating that:

While udica can create a good baseline policy from the container.json file, sometimes it might not be sufficient, and you will need customisations.
[...]
The kata-monitor daemonset required permissions to listen on a TCP socket and connect to a Unix socket. We had to redo the policy generation and enable network access.

I've added support for specifying additional TCP and UNIX socket permissions.

• Implemented the --tcp-connect option to specify additional TCP port permissions.
• Implemented the --unix-connect option to allow UNIX domain socket connect permissions.
• Modified policy generation logic to include these additional permissions in the generated policy file.

To easily test the changes:

# Add TCP and UNIX socket permissions to 'tests/test_basic.podman.json'
$ sudo udica -j test_basic.podman.json --tcp-connect 5432,636 --unix-connect test-container

# Verify that the new policies are added
$ cat test-container.cil | grep -E "(allow process (container_runtime_t|postgresql_port_t|ldap_port_t) \( (unix_stream_socket|tcp_socket) \( (connectto|name_connect) \)\))"

Thank you!
Fabien