Fix 'name' bug with v2 JFrog Artifactory

[alerickson]

PR Summary

Fixes bug where Find-PSResource using v2 Jfrog Artifactory is not returning the 'name' property of a module.

Previously, all package properties were pulled from the xml node m:properties, however title, listed as a child node under m:properties, can sometimes be empty. There is another title node that is a child of entry and as far as I can tell this node seems to always contain the name of the package.

Instead of pulling m:properties from the xml response, entry (which is the parent of m:properties) is now being used as the parent node from which all package metadata is parsed. This allows us to pull all of the information that was previously being retrieved from m:properties, but also get the extra title node mentioned above.

PR Context

Resolves #1534

PR Checklist

• [x] PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• [x] Summarized changes
• [x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• [x] This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • [x] None
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• User-facing changes
  • [x] Not Applicable
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• Testing - New and feature
  • [x] N/A or can only be tested interactively
  • OR
  • [ ] Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[alerickson]

@sean-r-williams please feel free to review if you like!

[sean-r-williams]

I just tested against my local Artifactory instance and this fix appears to be working as expected. Thanks a bunch for the fast turnaround @alerickson!

As an aside, would it be worthwhile to add steps to CI for testing PSResourceGet against additional feed providers? I don't know if this specific bug repro'd on cloud-hosted JFrog/Artifactory, but I imagine adding test suites running against other NuGet providers would help catch compat edge-cases between providers.

[alerickson]

@sean-r-williams completely agree, opened this issue up here #1536 so we can get some better CI testing for these scenarios. I'll work on that this week