Set preceding/succeeding pathType to range scope

[skooNI]

Moved this PR from provectus/kafka-ui#3933

• Breaking change? (if so, please describe the impact and migration path for existing application instances)
  Yes, but I'm not sure if anyone was using this correctly to begin with. See explanation below.

What changes did you make? (Give an overview)
#3259 introduced the ability to set the prefixType, however the preceedingPaths and succeedingPaths reference a variable that is out of scope of the range.

          {{- range .Values.ingress.succeedingPaths }}
          - path: {{ .path }}
            pathType: {{ .Values.ingress.pathType }}
            backend:
              service:
                name: {{ .serviceName }}
                port:
                  number: {{ .servicePort }}
          {{- end }}

In the range section, .Values.ingress.pathType refers to .Values.ingress.succeedingPaths[n].Values.ingress.pathType which I don't think was the intention.

This change switches it to .pathType, which refers to .Values.ingress.succeedingPaths[n].pathType, similar to path, serviceName, and servicePort variables.

Before this change in order to get the pathType set you'd need to configure the preceding/succeeding path to:

    succeedingPaths:
      - path: "/kafkaui/"
        Values:
          ingress:
            pathType: Prefix
        serviceName: kafkaui-service
        servicePort: 80

After this change it would reference be set by:

    succeedingPaths:
      - path: "/kafkaui/"
        pathType: Prefix
        serviceName: kafkaui-service
        servicePort: 80

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Set new schema value and verified helm deployment worked.

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)
Meet my dog Lupin!

[Haarolean]

@skooNI hey, sorry for the delay, figured out that I haven't been subscribed to this particular repo so far. We'll take a look

[Haarolean]

@skooNI thanks for your contribution!