Naming issues with moving the repository to a new location

[the-technat]

There has already been work gone into this topic in #421 and #441.

The following two lines still use the "old" repo path:

• https://github.com/argoproj-labs/terraform-provider-argocd/blob/main/main.go#L74
• https://github.com/argoproj-labs/terraform-provider-argocd/blob/main/go.mod#L1

old serve registry path

Not sure if this is simply a documentation issue or could lead to weird errors since users source the provider from registry.terraform.io/argoproj-labs/argocd instead of the in-code advertised registry.terraform.io/oboukili/argocd.

old go module path

As long as Github redirects from the old repository location to the new one this isn't an issue, but we should migrate and import our own packages from the new repo location to not depend on the redirection anymore.

This however is a chicken-egg situation as changing the module's import path in go.mod will fail everything and has to be merged to main before we can fix it by updating the pkg references.

[the-technat]

Regarding the go module path: I'm not sure what side-affects fixing this has. Theoretically in go's world this would require a major version bump which would change the import path to include /v8 as suffix. But since we are in Terraform's world things might work a bit different?

We can also just rely on Github's repository redirection forever and leave everything as is.

Anyone already had some experience with this?