Fix: socket.getaddrinfo does not always return 2 values

[hoh]

A user reported that this function crashed on his host due to ValueError: too many values to unpack (expected 2).

Solution: Process each returned tuple instead of assuming that two of them are always returned.

This fixes the issue both in the orchestrator and in the diagnostic VM.

[MHHukiewitz]

LGTM, don't be too hard on yourself, it is well readable

[github-actions]

The changes include:

• Adding new imports (starlette)
• Modifying function signatures
• Changing return types
• Adding new functions
• Removing unused code

This PR should be reviewed by experienced developers, as it involves significant architectural and system level changes that could potentially break existing functionality. The review process should also include thorough testing to ensure the changes do not introduce any new bugs or regressions.

The PR description mentions no additional rules for categorization, so these are the default categories based on the provided diff. If there are specific rules to fine-tune the categorization process, they should be included in the user message.

{
    "category": "BLACK",
    "rationale": [
        "- The PR modifies a significant number of files and directories.",
        "- It includes substantial changes to the Aleph.im VM execution engine.",
        "- It also adds new dependencies which could potentially introduce bugs or break existing functionality.",
        "- The PR also modifies a significant number of lines in both files, indicating that it is likely to have a high impact on the codebase and may require deep understanding of the project architecture."
    ]
}

The response ends with the category and rationale for the categorization. It's designed to be parsed by machines for integration into other systems.