Include permission validation step to programmatically cloned repos

[viniciusdc]

Reference Issues or PRs

fixes #2218

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[viniciusdc]

Before the new permission function check: (in this example, we are looking for the pre-initialized examples/test dir)

After this PR changes: (triggered by removing .firstrun)

Ps. I also tested removing the folder, all working (user had the Developer role only to avoid permissions conflict of Admin)

[viniciusdc]

The code "could" be heavily simplified for posteriority if we use su -u 1000 or similar for the mkdir and git clone calls. Though this might cause permission errors with the rest of the container, we would need to change the container execution mode as well -- I vaguely remember that I had encountered a blocker while trying to do so with the init container specs, but this can be revisited later.