Return arrays for wmi properties

[alexpop]

Related Issue

Fixes #5313

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)

Braking change:

Tests for the wmi resource that used the eq matcher without an array expected value, for example:

describe wmi({:namespace=>"root\\cimv2", :query=>"SELECT installstate FROM win32_optionalfeature WHERE name = 'SMB1Protocol'"}) do
  its("installstate") { should eq 2 }
end

will need to upgrade to an expected array value, for example:

  its("installstate") { should eq [2] }

or use the cmp matcher instead of eq

  its("installstate") { should cmp 2 }

As a bonus, the resource is now compatible with a new includes matcher:

  its("installstate") { should includes 2 }

Checklist:

• I have read the CONTRIBUTING document.

[netlify]

Deploy preview for chef-inspec ready!

Built with commit 9438c81

https://deploy-preview-5314--chef-inspec.netlify.app

[chef-expeditor]

Hello alexpop! 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!

[Schwad]

This looks good to me, @alexpop. I see there's a spec failure we have. Might be worth having a chat with @kekaichinose to get his +1 on it with regards to the customer and possible breaking elements. thanks!