Update host resource to resolve all ipaddresses

[AlanFoster]

Description

Aims to fix a regression introduced by #6045 where resolving DNS may return multiple ipaddresses:

PS > Resolve-DnsName -Type A dc1.example.demo.local | Select-Object -first 2 | ConvertTo-Json
[
    {
        "IP4Address":  "10.10.11.5",
        "Name":  "dc1.example.demo.locall",
        "Type":  1,
        "CharacterSet":  1,
        "Section":  0,
        "DataLength":  4,
        "TTL":  1200,
        "Address":  "10.10.11.5",
        "IPAddress":  "10.10.11.5",
        "QueryType":  1
    },
    {
        "IP4Address":  "10.0.2.15",
        "Name":  "dc1.example.demo.local",
        "Type":  1,
        "CharacterSet":  1,
        "Section":  0,
        "DataLength":  4,
        "TTL":  1200,
        "Address":  "10.0.2.15",
        "IPAddress":  "10.0.2.15",
        "QueryType":  1
    }
]

After the code change introduced by #6045 - the call to resolve_ipv4.inject(:merge) would evaluate to:

{"IP4Address"=>"10.0.2.15",                                                                           
 "Name"=>"dc1.example.demo.local",                                                                       
 "Type"=>1,                                                                                           
 "CharacterSet"=>1,                                                                                   
 "Section"=>0,
 "DataLength"=>4,
 "TTL"=>1200,
 "Address"=>"10.0.2.15",
 "IPAddress"=>"10.0.2.15",
 "QueryType"=>1}

Which causes the the 10.10.11.5 IPAddress to be dropped

Related Issue

#6045

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New content (non-breaking change)
• Breaking change (a content change which would break existing functionality or processes)

Checklist:

• I have read the CONTRIBUTING document.

[netlify]

✅ Deploy Preview for chef-inspec canceled.

Name	Link
🔨 Latest commit	eddcd2e
🔍 Latest deploy log	https://app.netlify.com/sites/chef-inspec/deploys/64063a59d33ca1000863e280

[chef-expeditor]

Hello AlanFoster! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes
   a. If everything looks good, one of them will approve it, and your PR will be merged.
   b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
   c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

[Vasu1105]

@AlanFoster there are failing tests could you please check if they can be fixed?

[ahasunos]

@AlanFoster
The changes looks good to me. Thanks.

The DCO test is failing because of the unsigned commit. You could sign the commit and push again.

[ahasunos]

thanks @AlanFoster

[AlanFoster]

Thanks for the approval 👍 Is there anything else needed for this to land?

[Vasu1105]

LGTM