Move the load balancer out of `loadbalancer` group and into a `network` group

[ADustyOldMuffin]

Somewhat breaking change we need to document well.

Here inside of the loadbalancer API definition

provider-digitalocean/apis/loadbalancer/v1alpha1/doc.go

Lines 17 to 22 in ee34f5c

	// Package v1alpha1 contains managed resources for DigitalOcean LoadBalancer
	// services.
	// +kubebuilder:object:generate=true
	// +groupName=loadbalancer.do.crossplane.io
	// +versionName=v1alpha1
	package v1alpha1

We should update the groupName to be network instead as well as rename the folder the file is in. This is because we're going to group the resources by their type and load balancer would fall into the inside the purview of networking stuff.

[amoghrajesh]

@ADustyOldMuffin I would like to work on this for Hacktoberfest. Could you provide a clear list of what is needed and assign the issue to me?

[ADustyOldMuffin]

Sure thing! The main thing is what was mentioned above, the groupName=loadbalancer.do.crossplane.io doesn't match other packages such as this one here.

The loadbalancer is apart of the Networking group of products and as such should be in that grouping, so that'd involve updating import references, the doc.go for it, and moving it's folder location. If you need any other information please let me know.

[amoghrajesh]

@ADustyOldMuffin I understand that the references do not match but what does grouping under a networking group mean? Can you share one reference where it grouped as?

[ADustyOldMuffin]

provider-digitalocean/examples/loadbalancer/loadbalancer.yaml

Line 1 in a4257b6

apiVersion: loadbalancer.do.crossplane.io/v1alpha1

It affects this field in the CRD.