Bump Podman to v5.6.3-dev

[podmanbot]

None

[ashley-cui]

LGTM

[Luap99]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, podmanbot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Luap99]

Btw do we really gain anything with these PRs other than pointless churn for us? To be clear I only mean bumping -dev on patch releases on the release branch, I definitely want to have the minor -dev bump on main.
cc @mheon

[mheon]

IMO, they're valuable because they tell us someone is running tip of branch vs stable tag. We don't get many people doing that on release branches, but it still seems nice to be alerted when it happens

[Luap99]

IMO, they're valuable because they tell us someone is running tip of branch vs stable tag. We don't get many people doing that on release branches, but it still seems nice to be alerted when it happens

Well how often would that happen AND actually matter? We have solid CI and on a release branch especially any commit should be good and ready to be releases any time. Why would it matter for debugging if they run release x.y.z or release x.y.z + a few more backported commits, the issue is likely not related to them doing that. And practically speaking any user who build podman can patch it regardless without us noticing. Many distro builds are patched to some level of degree.

All I am complaining about is that I have to look at this PR that doesn't add any meaningful value in my eyes and I have to keep pressing rerun here due the flakes (I know something we must address regardless)

[TomSweeneyRedHat]

FWIW, I'm not a fan of -dev versions in devoted release branches. But that's just my $.02.