Add versioned Libpod API paths to generated Swagger

[JJordan0C]

Summary

I came across #15376 and noticed it had been open for quite some time, so I decided to take a look.

This PR updates the generated Swagger specification so that Libpod API paths include the required version prefix.

Specifically, it:

• rewrites /libpod/... to /v{version}/libpod/...;
• keeps /libpod/_ping unversioned;
• reuses a required version path parameter;
• detects path collisions during generation;
• adds tests for the transformation.

This only affects Swagger generation and does not change the Podman daemon or API routing.

I hope this approach fits the project and helps address the issue. I’d appreciate any feedback or suggestions.

Fixes: #15376

Checklist

• Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• Referenced issues using Fixes: #15376 in commit message
• Tests have been added/updated
• Documentation has been updated (or no additional documentation changes are needed)
• All commits pass make validatepr
• Release note entered below

Does this PR introduce a user-facing change?

Generated Swagger documentation now includes the required version prefix for Libpod API endpoints.