Cause: The variables __podman_user and __podman_user_home_dir were being
set by both `vars` and `set_fact`. This causes unpredictable and
undefined behavior.

Consequence: When managing resources for two different users, the
variables __podman_user and __podman_user_home_dir were using the old
values from the first user, so config files for the first user were
being used for the second user.

Fix: Ensure that __podman_user is only ever set with `set_fact`, and
__podman_user_home_dir is only ever set with `vars`. Refactor the
code to use __podman_handle_user instead of __podman_user where a
`vars` could be used.

Result: Data for multiple users is kept separate.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>

1. 1. Summary by Sourcery

Prevent cross-user data contamination by introducing a dedicated __podman_handle_user variable for user tasks and using vars instead of set_fact for __podman_user_home_dir.

Bug Fixes:

• Stop mixing facts and vars for __podman_user and __podman_user_home_dir to avoid stale user data when managing multiple users

Enhancements:

• Refactor handle_user_group and include_tasks calls to use __podman_handle_user consistently
• Move __podman_user_home_dir assignment into vars blocks instead of set_fact