OpenVAS XML parser should create endpoints

[Whitehorse2]

Is your feature request related to a problem? Please describe

The greenbone/openvas scanner is normally scanning multiple targets at once. It is therefore important that the hosts or endpoints are also extracted correctly. A scan report can contain several IP addresses or, for example, a complete subnet. It is important that the hosts can be differentiated per endpoint, especially if there are several hundred hosts per report.

Describe the solution you'd like
The XML contains the data for host and port. These must be assigned accordingly by the parser.

Additional context
Examples over here: #11695

[Whitehorse2]

If I compare it with the endpoints of the OpenVas CSV parser, a domain name (as endpoint) is important in the data for searching/filtering. However, there should be the corresponding IP of the host/destination as the endpoint and in the findings. This is also not found in the OpenVAS CSV data. In my opinion, this is important for endpoint identification. #11695 (comment)

[valentijnscholten]

When looking at the code I can see the OpenVAS XML parser is creating endpoints. Are you seeing something different or seeing reports with more endpoint information that is not yet parsed? If you have a specific example we can take a look.