In the main datatable:
- Columns have been rearranged
- risks are reported with a RED background
- flows are marked OK or BAD, with icons
  (removing dedicated column)
- pkt counters and durations have been collapsed
  in single columns

- Add a "probe" column in the main datatable component
  reporting a "V" flag when the total L4_Payload of the
  flow has a _ZERO_ lenght. As such, it means that the flow
  relates to a "probe" (eg.: a single port-scan) and should
  be not of much interest
- In the table-proto, when displaying details about a row,
  a column l4_proto have been added

This commit add GeoIP support in the main flow table.
In order to easy visualization, the concept of
"INTERNAL networks" (aka: subnet related to "your"
system) is added and based on it, every flow is assigned
the "incoming" or "outgoing" classification.
Based on it, external system is identified and resolved in
terms of Country and ASN.

- FlowDataTable:
  - add a new "asn" column reporting "country" and "asn"
    related to external IP address
  - add two switches to ENABLE/DISABLE visibility of "incoming"
   and "outgoing" connections
  - add logic to retrieve internal network list, from the STORE,
    to check if connections are "incoming" or "outgoing"
  - "internal" IPs are reported on a light green background

- Home: a new "input field" have been added to input the
  comma separated list of "internal" subnets.
  When submitted, the list is transferred in the STORE, so to
  be available to other components

- store.js
  - cleaned, and configured to host "ourNetworks" array,
    containing every single subnet of our internal systems