Updated Path property target type serialization.

[mikeurbach]

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• Bugfix

Desired Merge Strategy

• Squash: The PR will be squashed and merged (choose this if you have no preference).

Release Notes

This includes two changes to how Path property target types are serialized:

• For ModuleTargets, use the OMInstanceTarget target type, like for InstanceTargets
• Add a new API to request "member" target types

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
• Did you mark the proper milestone (Bug fix: 3.5.x, 3.6.x, or 5.x depending on impact, API modification or big change: 6.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[jackkoenig]

Meta point, should this be exposed as isMemberPath? Is there a more descriptive name we could give to the behavior? @albertchen-sifive @mikeurbach

[mikeurbach]

Meta point, should this be exposed as isMemberPath? Is there a more descriptive name we could give to the behavior?

I think isMemberPath is better. Maybe for full granularity it could be something like isMemberTargetType, but I don't know how useful "target type" is in the name.