Add Support for HTTP Request Fingerprinting

[biandratti]

Problem:
The current implementation lacks support for identifying HTTP request signatures from older browsers (e.g., MSIE5), command-line tools (e.g., curl, wget), crawlers, mobile devices, and gaming consoles. These clients often send unique User-Agent and other HTTP headers that can help identify the application and platform. However, without proper fingerprinting for these cases, the system misses the opportunity to identify older or uncommon clients, which could be essential for tasks such as traffic analysis, security, and troubleshooting.

Details:
p0f's official documentation suggests that HTTP request signatures are especially important for identifying clients like:

Older Browsers (e.g., MSIE5, Netscape Navigator).
Command-line Tools (e.g., curl, wget).
Crawlers and Bots (e.g., Googlebot, Bingbot).
Mobile Devices (e.g., iOS, Android).
Gaming Consoles (e.g., PlayStation, Xbox).
To collect accurate signatures, p0f can either run on the client system itself or analyze the traffic between the client and the web server. The goal is to capture and parse key headers in the HTTP request to identify the client application and platform.

Example from p0f:

.-[ 1.2.3.4/1524 -> 4.3.2.1/80 (http request) ]-
|
| client   = 1.2.3.4/1524
| app      = Firefox 5.x or newer
| lang     = English
| params   = none
| raw_sig  = 1:Host,User-Agent,Accept=[text/html,application/xhtml+xml...
|
`----

The goal is to implement logic that captures these specific client signatures and integrates them into the overall HTTP request fingerprinting process. The parser from database was already done.

pub struct P0fOutput {
    pub syn: Option<SynTCPOutput>,
    pub syn_ack: Option<SynAckTCPOutput>,
    pub mtu: Option<MTUOutput>,
    pub uptime: Option<UptimeOutput>,
    pub http_request: Option<HTTPRequestOutput>, // New field
}