@W-21771476: feat: display HasVpi in package version list and report commands [DO NOT MERGE until 6/4 262.8 deploy]

[tporcaro-sf]

@W-21771476@

Summary

• Display HasVpi field in sf package version list --verbose and sf package version report
• Version-gated at API v67+ (column/row absent at lower versions)
• List displays 'true'/'false'/'N/A' (unlocked); Report displays 'Yes'/'No'/'N/A'
• JSON schemas updated

Dependencies

• Requires forcedotcom/packaging#875 to merge first (publishes new @salesforce/packaging version)
• Requires W-21771475 (262.8 patch) to be fully deployed (scheduled 6/4)
• After packaging merges, this PR needs a dep bump commit before merge

Test plan

• Unit tests: report massage transforms (managed→Yes, unlocked→N/A, undefined stays undefined)
• Schema validation passing
• NUT: HasVpi key present in verbose json output (conditional on org API version)
• Manual testing on 262 devhub (hub0318) and 260 devhub (hub1215)

🤖 Generated with Claude Code

[salesforce-cla]

Thanks for the contribution! It looks like @tjporcaro is an internal user so signing the CLA is not required. However, we need to confirm this.

[tporcaro-sf]

⚠️ CI compile failure is expected — @salesforce/packaging on npm doesn't have the HasVpi type yet.

Once forcedotcom/packaging#875 merges and publishes, I'll bump the dep here and CI will go green.

cc: @KSCCO @shetzel

[tporcaro-sf]

Note: "Has Version Settings" label reviewed/approved by Joanna Nolasco

cc: @KSCCO @shetzel

[KSCCO]

It seems inconsistent that list returns true/false and report returns yes/no. Is there a reason for that?

[tporcaro-sf]

It seems inconsistent that list returns true/false and report returns yes/no. Is there a reason for that?

@KSCCO No Solid reason. I think it was to make it consistent with Managed Metadata Removed: Yes/No in the report. But other fields in the report like Code Coverage Met: use true/false so it seems we can do that instead and be consistent between the list and the report. I'll make the change.

[tporcaro-sf]

@KSCCO Updated — report now displays true/false (consistent with list and Code Coverage Met). See commit e9a8849.

[KSCCO]

lgtm
Is all the reformatting in package-version-report.json intended? I don't know what the style guidelines are.

[tporcaro-sf]

@KSCCO Yes — prettier reformatted the schema file when it was touched by the pre-commit hook. The only functional change is the addition of the HasVpi property at the end. The rest is prettier collapsing multi-line arrays to single lines (e.g., "type": [\n "boolean",\n "string"\n] → "type": ["boolean", "string"]).