Keep the same level of privileges when running with rootless: False

[BenjaminSchubert]

This fixes multiple bugs:

• Create/destroy, wait on the previous task as root too. Otherwise the
  task fails, as it doesn't have access to the job

• Build the image with the same user

Notes

• I am not sure how to test that, and ensure it doesn't break again. Any advice would be much appreciated
• Using rootless: False would still fail with a similar error as CONTAINER_HOST presence prevents ansible from gathering facts on podman containers #15

[BenjaminSchubert]

Alternatively, we could also only become root for the commands requiring podman, so that sudo rules could be simpler

[sshnaidm]

TBH all this rootless/rootfull config seems redundant there and doesn't really work. I think we need just to run molecule with sudo to get rootfull containers to work.

[ssbarnea]

I am inclined to agree with @sshnaidm on this and I do have two additional issues to point:

• if we use become only on some tasks we are prone to get surprises
• using default(true) would be bad because ansible default is false, not true.

[ssbarnea]

Closing as this is unlikely to be merged in current form. Still, I am open to suggestion for improving the experience, like detecting when root is needed and missing and warning the user. Still, I do think that the default behavior of using non-root is better from the security point of view.