chore: update references for old repository name

[mugdha-adhav]

Related to #105

Updating references for csi-driver-image to container-image-csi-driver in the listed files/packages.

• go.mod
• package imports
• Dockerfiles
• docs
• scripts

[mugdha-adhav]

Waiting on CI builds to be fixed in #126 before we merge this PR.

[mbtamuli]

Not sure why it's not getting triggered in your case. Maybe it's related to the repository name/branch changes. I had updated the HEAD for both origin and upstream as opposed to just origin as mentioned here - https://github.com/warm-metal/container-image-csi-driver#note-for-forked-repositories

git branch -m master main
git remote set-url upstream [email protected]:warm-metal/container-image-csi-driver.git
git remote set-url origin [email protected]:mbtamuli/container-image-csi-driver.git
git fetch origin
git fetch upstream
git branch -u main main
git remote set-head origin -a
git remote set-head upstream -a

Are you sure you've updated your fork correctly? For #126, the workflows are getting triggered.

[mugdha-adhav]

Are you sure you've updated your fork correctly? For #126, the workflows are getting triggered.

I think the workflows got triggered for #126 because it had the changes to fix the CI. As for updating my fork, I re-created my fork after name change so I don't think the issue is related to my fork.

And now the workflows got triggered after I rebased this PR with your CI changes.

[mbtamuli]

container-image-csi-driver/.devcontainer/devcontainer.json

Line 4 in 03636ae

"image": "ghcr.io/warm-metal/csi-driver-image/devcontainer:latest",

@mugdha-adhav Please change the name as well in your PR

-	"image": "ghcr.io/warm-metal/csi-driver-image/devcontainer:latest",
+	"image": "ghcr.io/warm-metal/container-image-csi-driver/devcontainer:latest",

[mugdha-adhav]

@mugdha-adhav Please change the name as well in your PR

Not just the name, but I think we'll also need to update all the references of csi-driver-image in the devcontainer.json files. Working on it.

[mugdha-adhav]

I tried updating all references of older repository in a single PR, but it's getting too large and hard to track.

Reverted some of the recent commits. Will create separate PRs for those changes.

@mbtamuli JFYI, your dev-container related change will also go in one of the follow up PR.

[mbtamuli]

your dev-container related change will also go in one of the follow up PR.

@mugdha-adhav I understand. I'll take care of raising a PR related to any devcontainer updates.