feat(outdated): support monorepo tag nameing convention

[kevinbeier-enbw]

What

apm outdated and apm marketplace outdated now understand monorepo-style git tags like my-package_v1.0.1, not only v1.0.0.

Why

Repos that tag per package often use package_v1.0.0. Before this change, APM treated those refs as branch names, so outdated showed unknown instead of a real Latest / Status.

Idea is when you have a monorepo with multiple apm's

examples/monorepo-multi-apm/
├── README.md
├── TAGGING.md
├── apm.yml                      # marketplace index (apm1 + apm2)
└── packages/
    ├── apm1/
    │   ├── apm.yml
    │   └── .apm/skills/hello/SKILL.md
    └── apm2/
        ├── apm.yml
        └── .apm/skills/hello/SKILL.md

Note

We use _v (e.g. api-governance_v1.0.2), not @, because @ is already used for marketplace installs (apm install pkg@my-marketplace). If any other prefered standard is wanted, this can be changed.

[kevinbeier-enbw]

@microsoft-github-policy-service agree company="EnBW"

[Copilot]

Copilot wasn't able to review any files in this pull request.