feat: patchable init mirroring

[dervoeti]

Fixes #1049

This adds the --mirrored flag to patchable init. It assumes that a mirror repository already exist, pushes the ref specified via --base to the mirror and configures the mirrorer repo as upstream in patchable.toml.
As discussed with @lfrancke, we want to fork the repos in the stackabletech org and use forks instead of clones (the latter decision was not a strong opinion, I decided to go with forks since they would facilitate back-contributions).

I created mirror repositories (forks in our case) for all our products and synced the tags for all versions we use. I updated all patchable.toml files to use the mirror repositories (with the exception of Omid 1.1.3-SNAPSHOT, which is a temporary version we don't ship).

I had to drop the usage of FETCH_HEAD, since it caused problems when running patchable init for a tag/branch that for some reason was already present in the local Git repo. The problem is that FETCH_HEAD is empty in that case, I think that's due to no changes being fetched.

[nightkr]

As a nomenclature thing, I think I prefer calling this mirroring instead.

[dervoeti]

As a nomenclature thing, I think I prefer calling this mirroring instead.

Had the same thought when opening the PR 🙂 Will refactor it.

[dervoeti]

@nightkr I would now go ahead and update all the patchable.toml files (create product-level configs and adapt the version-level configs). And update this PR to be compatible with the current main branch.

[nightkr]

Sounds good to me.

[dervoeti]

@nightkr This is done now. Product-level configs are all there and I removed upstream from version-level configs and added mirror instead.

[nightkr]

All versions seem to check out fine (ls **/stackable/patches | insert version { ls $in.name -s | filter { $in.type == "dir" } | get name } | insert product { $in.name | path dirname -n 2 } | flatten | each { cargo patchable checkout $in.product $in.version }).

[dervoeti]

@nightkr I noticed on more thing 🙁 Some builds would fail, because we use patchable checkout inside Docker to checkout the source before building the product. For this, the product config is needed.
At least for some images we only copy the specific version directory, which of course does not include the product config. I'll change that, so that the whole patches directory is copied into the image, not just the directory for the specific version.

[nightkr]

Ahh, right. Good catch.

[dervoeti]

@nightkr Fixed in 6148608

[nightkr]

Hm, that would mean losing caching for all versions when any version is modified, though. It should be enough to copy patches/$version and patches/patchable.toml.

[dervoeti]

@nightkr Reverted and fixed by copying only the product config