Rework flow breed (#2926)

Right now, there is, in essence, a static mapping between flow protocols
and flow breeds.
Make it dynamic: allow to have different flows, with the same
classification but differents breeds. This is the same logic that we
already have for categories....

Preliminary work to support breed in category lists.

API change from the app POV: to get the flow breed don't use anymore
`ndpi_get_proto_breed()`, but access directly `struct ndpi_proto->breed`

The functions `ndpi_domain_classify_*()` and
`ndpi_get_host_domain_suffix()` now have a `u_int32_t` parameter as
`class_id` (instead of `u_int_16_t`), with the following logic:
```
class_id = (breed << 16) | category
```
instead of the old:
```
class_id = category
```
Please note that this change is back-compatible: if you are not
interested into breeds, you don't need to update the application code.

tests/cfgs/disable_use_client_port/result/iphone.pcap.out

@@ -37,10 +37,10 @@ AppleiCloud	209	126365	5
 AppleiTunes	62	23299	2
 Spotify	2	172	1
 
+Unrated                          2 120           1            
 Safe                           132 53116         8            
 Acceptable                     288 144245        39           
 Fun                             64 23471         3            
-Unrated                          2 120           1            
 
 Unspecified                      2 120           1            
 Web                            332 178040        12