Decouple security enabled from reverse proxying functionality

[bnevis-i]

🚀 Feature Request

Relevant Package [REQUIRED]

internal

Description [REQUIRED]

Issue edgexfoundry/edgex-helm#22 explains the problem in detail.

Describe the solution you'd like

In EdgeX 3.0, all microservices take a JWT for authentication. Therefore, the following functionality that routes requests differently should be decoupled from secure mode. Specifically, there should be separate switches the enable JWT processing and backend routing through the API gateway.

	for prefix := range clientsMapping {
		if strings.HasPrefix(path, prefix) {
			if common.IsSecurityEnabled() {
				app.secure(w, r)
				return
			}
			originalPath := strings.TrimPrefix(path, prefix)
			targetAddr := clientsMapping[prefix]
			insecure(w, r, originalPath, targetAddr)
		}
	}

Note that in insecure mode, edgex-ui-go works as normal. In the helm deployment, we would like to do service routing via kubernetes, instead of the API gateway, to fix this bug.

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?