feat(upgrade_to_v3): add migration for moving configuration keys from Fluentd to sumologic

[kkujawa-sumo]

Migration for change introduced in SumoLogic/sumologic-kubernetes-collection#2635

[swiatekm]

The logic looks good to me, just had some nitpicks about naming.

[kkujawa-sumo]

@swiatekm-sumo please take another look

[swiatekm]

LGTM, 🙈 about the v2 and v3 names

[kkujawa-sumo]

LGTM, 🙈 about the v2 and v3 names

Personally I mixed feelings about removing v2 an v3 for example here:

func createSumologicLogs(fluentdLogsV2 *FluentdLogs, sumologicLogsV2 *SumologicLogsV2) *SumologicLogsV3 {
	sumologicLogsV3 := &SumologicLogsV3{}

	if fluentdLogsV2 != nil {
		sumologicLogsV3.Container = createSumologicLogsContainer(fluentdLogsV2.Containers, sumologicLogsV2.Container)
		sumologicLogsV3.Systemd = createSumologicLogsConfig(fluentdLogsV2.Systemd, sumologicLogsV2.Systemd)
		sumologicLogsV3.Kubelet = createSumologicLogsConfig(fluentdLogsV2.Kubelet, nil) // set nil because in v2 there was not any configuration under sumologic.logs.kubelet
		sumologicLogsV3.Default = createSumologicLogsConfig(fluentdLogsV2.Default, nil) // set nil because in v2 there was not any configuration under sumologic.logs.defaultFluentd
	}

	if sumologicLogsV2 != nil {
		sumologicLogsV3.Rest = sumologicLogsV2.Rest
	}
	return sumologicLogsV3
}

this function take sumologicLogsV2 and using this information creates sumologicLogsV3

[kkujawa-sumo]

I changed to the "new style" and now all V2 in names are changed to Input and all V3 are changed to Output 🎉